← previous blocknext block →recent activity
Analyzing
Block #76,256,284
15 transactions · 14 stateful · 2026-05-22 11:57:14 UTC
Parallelism
80/100
Blocked
21%
Avg conflicts / tx
0.53
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,256,284 · 15 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
1w02w04w05w18w011w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb9d8189…e926
0xa6afd3…d132
6 touches
3 conflicts
0x3a6e7600…e1f1
0xa6afd3…d132
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x5db622da…8223
0xd32edf…ff58
3 touches
1 conflict
0x32769b3f…976f
0xa6afd3…d132
3 touches
1 conflict
0x7c938264…ae10
0xa6afd3…d132
3 touches
1 conflict
0x8cf3d245…1d0d
0x1d1325…2305
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 0xdb9d8189a0…88e926
Audit this contract →
← previous block·next block →recent activity