← previous blocknext block →recent activity
Analyzing
Block #76,602,967
25 transactions · 17 stateful · 2026-05-24 02:25:31 UTC
Parallelism
80/100
Blocked
41%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,602,967 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w08w19w211w012w013w114w217w320w223w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf722d24e…ac24
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x03226734…d6d2
0xa6afd3…d132
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0xf282c2b3…28b4
0xa6afd3…d132
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xca2bf828…9937
0xd32edf…ff58
5 touches
3 conflicts
0xea7ebe9d…709e
0x1d1325…2305
4 touches
1 conflict
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: Perpl
3 conflicts on slot 0xf722d24e14…a9ac24
Audit this contract →
← previous block·next block →recent activity