← previous blocknext block →recent activity
Analyzing
Block #77,579,225
11 transactions · 7 stateful · 2026-05-28 14:49:56 UTC
Parallelism
73/100
Blocked
29%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #77,579,225 · 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
1w02w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13350543…ebf2
0xa6afd3…d132
4 touches
1 conflict
0x78ce7d20…2a3f
0xa6afd3…d132
4 touches
1 conflict
0xc2e3614f…1a32
0xa6afd3…d132
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x7f083417…88f4
0xa6afd3…d132
3 touches
1 conflict
0x84480a79…aa61
0xa6afd3…d132
3 touches
1 conflict
0x8d35caaa…7a59
0x065c9d…c394
2 touches
0 conflicts
0xce827910…ff22
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
1 conflict on slot 0x1335054358…6bebf2
Audit this contract →
← previous block·next block →recent activity