← previous blocknext block →recent activity
Analyzing
Block #86,955,462
22 transactions · 22 stateful · 2026-07-11 01:30:01 UTC
Parallelism
77/100
Blocked
45%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,955,462 · 22 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
1w02w13w14w26w37w012w013w114w215w317w418w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xab98deda…aec3
0x34b655…2a6f
8 touches
6 conflicts
0x5fcf45b9…4161
0xd32edf…ff58
7 touches
6 conflicts
0xab98deda…aec4
0x34b655…2a6f
6 touches
3 conflicts
0x4e66a473…9fe8
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity