← previous blocknext block →recent activity
Analyzing
Block #84,562,956
11 transactions · 10 stateful · 2026-06-29 23:26:01 UTC
Parallelism
73/100
Blocked
30%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,562,956 · 11 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
2w03w15w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5bdb0bbb…f5a2
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x826cce18…251c
0x34b655…2a6f
4 touches
1 conflict
0x09a15b10…2639
0x754704…b603
4 touches
1 conflict
0x5149ba0e…d954
0x754704…b603
4 touches
1 conflict
0x0b0c2e8d…c1b8
0xe52b14…7230
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 0x5bdb0bbb37…04f5a2
Audit this contract →
← previous block·next block →recent activity