← previous blocknext block →recent activity
Analyzing
Block #76,229,656
22 transactions · 20 stateful · 2026-05-22 09:00:01 UTC
Parallelism
77/100
Blocked
50%
Avg conflicts / tx
1.05
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,229,656 · 22 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
1w02w13w26w07w18w29w310w411w012w215w420w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0x9fc6ea79…e2dc
0x34b655…2a6f
10 touches
10 conflicts
0xadcc6a38…4ef1
0x34b655…2a6f
6 touches
3 conflicts
0x65e795ca…0320
0x34b655…2a6f
6 touches
3 conflicts
0x005fb969…2d97
0x34b655…2a6f
6 touches
3 conflicts
0x085df2c1…305a
0x34b655…2a6f
6 touches
3 conflicts
0x3c35979a…975d
0x34b655…2a6f
6 touches
3 conflicts
0x39da55ef…42d5
0x34b655…2a6f
6 touches
3 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