You are right, this will block the row regardless of isolation level. With MVCC, you can get consistent reads without locks, but you need locks when writing.
The second transaction will wait for the first to complete (for example: COMMIT or ROLLBACK ) before trying to do anything. Therefore, in this case, the cursor on T2 βfreezesβ in the update, waiting for the completion of T1.
You will receive a new SCN after completing T1, and another after completing T2.
source share