← previous blocknext block →recent activity
Analyzing
Block #83,202,159
13 transactions · 12 stateful · 2026-06-23 16:09:35 UTC
Parallelism
77/100
Blocked
17%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,202,159 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x731e6d82…2883
0x065c9d…c394
4 touches
1 conflict
0x774c9fc0…1bc5
0x065c9d…c394
4 touches
1 conflict
0x7ed6373c…a3e9
0x065c9d…c394
4 touches
1 conflict
0x07837580…6e86
0x065c9d…c394
2 touches
0 conflicts
0x2141d45f…0f1a
0x065c9d…c394
2 touches
0 conflicts
0x30e8cab8…d864
0x065c9d…c394
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Kuru Exchange: MarginAccount
1 conflict on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity