← previous blocknext block →recent activity
Analyzing
Block #84,594,409
12 transactions · 11 stateful · 2026-06-30 02:55:38 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,594,409 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w19w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x600e842c…4a69
0x34b655…2a6f
6 touches
3 conflicts
0xf1e0175c…5649
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x9a89094e…f5b2
0x34b655…2a6f
6 touches
3 conflicts
0x7f93f2f0…6666
0x34b655…2a6f
6 touches
3 conflicts
0x6eb3e5af…064e
0x34b655…2a6f
6 touches
3 conflicts
0x7688287c…7f8a
0x34b655…2a6f
4 touches
1 conflict
0x6b47245e…a342
0x34b655…2a6f
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 0x600e842c72…c64a69
Audit this contract →
← previous block·next block →recent activity