← previous blocknext block →recent activity
Analyzing
Block #76,256,261
13 transactions · 11 stateful · 2026-05-22 11:57:05 UTC
Parallelism
69/100
Blocked
45%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,256,261 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w16w29w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a6e7600…e1f1
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xdb9d8189…e926
0xa6afd3…d132
4 touches
1 conflict
0x8cf3d245…1d0d
0x1d1325…2305
2 touches
0 conflicts
0xdb067026…9eb8
0x1d1325…2305
2 touches
0 conflicts
0x99a21305…dffc
0x2a68ba…90c5
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 0x3a6e7600b5…c1e1f1
Audit this contract →
← previous block·next block →recent activity