← previous blocknext block →recent activity
Analyzing
Block #84,512,426
18 transactions · 15 stateful · 2026-06-29 17:48:37 UTC
Parallelism
61/100
Blocked
60%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #84,512,426 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w26w07w18w29w311w413w514w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xacbc3fbb…fe8e
0x34b655…2a6f
10 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x9277f32c…01c6
0x34b655…2a6f
6 touches
3 conflicts
0xc5f79d92…ddf9
0x34b655…2a6f
6 touches
3 conflicts
0xe02484a6…c32e
0xc8689a…ee79
6 touches
3 conflicts
0x3766925b…76fe
0x34b655…2a6f
6 touches
3 conflicts
0x49b0842d…0a93
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 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity