← previous blocknext block →recent activity
Analyzing
Block #84,535,586
20 transactions · 7 stateful · 2026-06-29 20:23:00 UTC
Parallelism
85/100
Blocked
29%
Avg conflicts / tx
0.1
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,535,586 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc33f8dc7…d87f
0x34b655…2a6f
4 touches
1 conflict
0xf95f86cd…e927
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x39cc2185…caca
0x34b655…2a6f
4 touches
1 conflict
0x48315f67…c1a6
0x34b655…2a6f
4 touches
1 conflict
0x0605d00c…5336
0x34b655…2a6f
3 touches
1 conflict
0xb24fdf65…4d35
0x34b655…2a6f
3 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
1 conflict on slot 0xc33f8dc756…d5d87f
Audit this contract →
← previous block·next block →recent activity