← previous blocknext block →recent activity
Analyzing
Block #84,494,857
22 transactions · 17 stateful · 2026-06-29 15:51:22 UTC
Parallelism
82/100
Blocked
53%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,494,857 · 22 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
1w02w13w24w37w08w19w211w012w113w215w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3732c6c9…ded6
0x34b655…2a6f
6 touches
3 conflicts
0xe02484a6…c32e
0xc8689a…ee79
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xe2e45419…f17b
0x34b655…2a6f
6 touches
3 conflicts
0xb6836671…5c3c
0x34b655…2a6f
6 touches
3 conflicts
0x44966858…1d1a
0x34b655…2a6f
6 touches
3 conflicts
0xb092a686…de43
0xd32edf…ff58
5 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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 0x3732c6c93a…02ded6
Audit this contract →
← previous block·next block →recent activity