← previous blocknext block →recent activity
Analyzing
Block #84,512,572
24 transactions · 19 stateful · 2026-06-29 17:49:36 UTC
Parallelism
79/100
Blocked
53%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,512,572 · 24 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
1w02w15w26w37w08w19w010w111w212w313w415w016w122w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x2dcd67e4…92f6
0xd32edf…ff58
7 touches
6 conflicts
0x49b0842d…0a93
0x34b655…2a6f
6 touches
3 conflicts
0x3766925b…76fe
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xacbc3fbb…fe8e
0x34b655…2a6f
6 touches
3 conflicts
0xc5f79d92…ddf9
0x34b655…2a6f
6 touches
3 conflicts
0xf95f86cd…e927
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 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity