← previous blocknext block →recent activity
Analyzing
Block #77,351,012
11 transactions · 11 stateful · 2026-05-27 13:29:44 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #77,351,012 · 11 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
2w03w16w28w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xc51d3663…0f45
0xa6afd3…d132
6 touches
3 conflicts
0xd71a331e…42ea
0xa6afd3…d132
6 touches
3 conflicts
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x0b8e2de4…f5f6
0x065c9d…c394
2 touches
0 conflicts
0x10e9f199…41bf
0x065c9d…c394
2 touches
0 conflicts
0x1801d156…aa69
0x065c9d…c394
2 touches
0 conflicts
0x18cf3003…51d1
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: 0xa6afd386…b0d132
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity