← previous blocknext block →recent activity
Analyzing
Block #76,482,550
10 transactions · 8 stateful · 2026-05-23 13:03:43 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,482,550 · 10 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
1w03w14w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3afb222…4d17
0xa6afd3…d132
6 touches
3 conflicts
0xb3572c95…9c4a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x99a4d286…ad43
0xa6afd3…d132
4 touches
1 conflict
0x0c8ec6b9…cc32
0x065c9d…c394
2 touches
0 conflicts
0x0e496846…3e66
0x065c9d…c394
2 touches
0 conflicts
0x18cf3003…51d1
0x065c9d…c394
2 touches
0 conflicts
0x5c3a108d…72bd
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 0xc3afb2229f…7f4d17
Audit this contract →
← previous block·next block →recent activity