← previous blocknext block →recent activity
Analyzing
Block #86,853,623
26 transactions · 20 stateful · 2026-07-10 14:09:14 UTC
Parallelism
81/100
Blocked
50%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,853,623 · 26 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
1w02w13w27w08w19w213w314w015w318w119w220w324w025w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc61f831e…e236
0x34b655…2a6f
8 touches
6 conflicts
0x0dbf9688…c6cf
0x43cf54…7777
8 touches
6 conflicts
0xabd188aa…aff6
0xd32edf…ff58
7 touches
6 conflicts
0x5f14622f…73ee
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x0d05c2b3…bd7e
0x34b655…2a6f
6 touches
3 conflicts
0x0d05c2b3…bd7f
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 0xc61f831e46…efe236
Audit this contract →
← previous block·next block →recent activity