← previous blocknext block →recent activity
Analyzing
Block #76,550,727
33 transactions · 29 stateful · 2026-05-23 20:37:45 UTC
Parallelism
79/100
Blocked
59%
Avg conflicts / tx
1.45
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #76,550,727 · 33 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w38w49w510w611w012w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
14 touches
21 conflicts
0x2dc020c7…0697
0xc8689a…ee79
12 touches
15 conflicts
0x3199a6b2…eb67
0xa6afd3…d132
12 touches
15 conflicts
0x40970e69…da50
0x1d1325…2305
12 touches
15 conflicts
0xa987699f…eabe
0x1d1325…2305
12 touches
15 conflicts
0x169d60cf…e576
0xa6afd3…d132
12 touches
15 conflicts
0xad3ef711…4f2b
0x1d1325…2305
12 touches
15 conflicts
0x99a21305…dffc
0x2a68ba…90c5
12 touches
15 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
21 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity