← previous blocknext block →recent activity
Analyzing
Block #76,550,571
29 transactions · 24 stateful · 2026-05-23 20:36:42 UTC
Parallelism
79/100
Blocked
46%
Avg conflicts / tx
0.93
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #76,550,571 · 29 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
2w06w17w08w110w211w312w413w514w015w116w217w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc56294b3…4af5
0xa6afd3…d132
12 touches
15 conflicts
0x799516ce…2c47
0xa6afd3…d132
10 touches
10 conflicts
0xa0bd005c…fd02
0xa6afd3…d132
10 touches
10 conflicts
0x8cf3d245…1d0d
0x1d1325…2305
10 touches
10 conflicts
0xdb067026…9eb8
0x1d1325…2305
10 touches
10 conflicts
0xea7ebe9d…709e
0x1d1325…2305
10 touches
10 conflicts
0x99a21305…dffc
0x2a68ba…90c5
10 touches
10 conflicts
0xe2e94dfa…5026
0x2a68ba…90c5
10 touches
10 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
15 conflicts on slot 0xc56294b31f…664af5
Audit this contract →
← previous block·next block →recent activity