← previous blocknext block →recent activity
Analyzing
Block #84,489,004
21 transactions · 18 stateful · 2026-06-29 15:12:17 UTC
Parallelism
76/100
Blocked
39%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,489,004 · 21 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
1w03w05w06w111w012w113w214w115w316w017w119w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x75291f8b…3ac0
0x34b655…2a6f
8 touches
6 conflicts
0xee757899…302b
0x34b655…2a6f
6 touches
3 conflicts
0x44931115…3703
0x34b655…2a6f
6 touches
3 conflicts
0x44966858…1d1a
0x34b655…2a6f
6 touches
3 conflicts
0x3732c6c9…ded6
0x34b655…2a6f
6 touches
3 conflicts
0xe02484a6…c32e
0xc8689a…ee79
6 touches
3 conflicts
0xe99d8e68…a16e
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
6 conflicts on slot 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity