← previous blocknext block →recent activity
Analyzing
Block #76,723,431
14 transactions · 12 stateful · 2026-05-24 15:47:10 UTC
Parallelism
71/100
Blocked
42%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,723,431 · 14 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
1w02w13w24w06w27w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa0bd005c…fd02
0xa6afd3…d132
8 touches
6 conflicts
0x9f608e7b…0b4e
0xa6afd3…d132
6 touches
3 conflicts
0x99a21305…dffc
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x3484c9df…bfd5
0x1d1325…2305
2 touches
0 conflicts
0x4e804b48…ef71
0x1d1325…2305
2 touches
0 conflicts
0x8cf3d245…1d0d
0x1d1325…2305
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
6 conflicts on slot 0xa0bd005c40…3bfd02
Audit this contract →
← previous block·next block →recent activity