← previous blocknext block →recent activity
Analyzing
Block #76,559,347
25 transactions · 19 stateful · 2026-05-23 21:35:16 UTC
Parallelism
76/100
Blocked
53%
Avg conflicts / tx
0.96
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #76,559,347 · 25 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
5w06w17w28w39w010w111w212w313w414w415w516w020w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0x99a21305…dffc
0x2a68ba…90c5
8 touches
6 conflicts
0xb5c4826d…bdd6
0x1d1325…2305
8 touches
6 conflicts
0x03226734…d6d2
0xa6afd3…d132
8 touches
6 conflicts
0x8cf3d245…1d0d
0x1d1325…2305
8 touches
6 conflicts
0x2dc020c7…0697
0xc8689a…ee79
8 touches
6 conflicts
0xddf0e471…ce9d
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity