← previous blocknext block →recent activity
Analyzing
Block #84,571,405
12 transactions · 11 stateful · 2026-06-30 00:22:22 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,571,405 · 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
4w05w06w19w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x086db8fc…0024
0x34b655…2a6f
8 touches
6 conflicts
0xa7e2f1b7…7e6f
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0aa5b76b…60db
0x34b655…2a6f
6 touches
3 conflicts
0x801058a8…5bc3
0x34b655…2a6f
5 touches
3 conflicts
0x2c75ca93…a569
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
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
6 conflicts on slot 0x086db8fc6e…830024
Audit this contract →
← previous block·next block →recent activity