← previous blocknext block →recent activity
Analyzing
Block #76,594,212
15 transactions · 15 stateful · 2026-05-24 01:27:14 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
1.07
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,594,212 · 15 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
2w03w14w25w36w07w18w29w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x03226734…d6d2
0xa6afd3…d132
8 touches
6 conflicts
0x3a6e7600…e1f1
0xa6afd3…d132
8 touches
6 conflicts
0xf282c2b3…28b4
0xa6afd3…d132
8 touches
6 conflicts
0x2dc020c7…0697
0xc8689a…ee79
8 touches
6 conflicts
0x99a21305…dffc
0x2a68ba…90c5
8 touches
6 conflicts
0x10abefc9…c9bc
0x1d1325…2305
8 touches
6 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: Perpl
10 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity