← previous blocknext block →recent activity
Analyzing
Block #76,732,264
19 transactions · 14 stateful · 2026-05-24 16:45:55 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
0.74
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #76,732,264 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w07w18w29w310w011w113w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x169d60cf…e576
0xa6afd3…d132
6 touches
3 conflicts
0x9f608e7b…0b4e
0xa6afd3…d132
6 touches
3 conflicts
0xa0bd005c…fd02
0xa6afd3…d132
6 touches
3 conflicts
0xdb067026…9eb8
0x1d1325…2305
4 touches
1 conflict
0xea7ebe9d…709e
0x1d1325…2305
4 touches
1 conflict
0x99a21305…dffc
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity