← previous blocknext block →recent activity
Analyzing
Block #86,909,524
10 transactions · 9 stateful · 2026-07-10 20:23:08 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,909,524 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4b8c5b1…836b
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x26c3abf6…249d
0x34b655…2a6f
2 touches
0 conflicts
0x57e0b825…eb63
0x34b655…2a6f
2 touches
0 conflicts
0x5fee1ba0…2520
0x34b655…2a6f
2 touches
0 conflicts
0x706f7b10…8e2f
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xb4b8c5b109…eb836b
Audit this contract →
← previous block·next block →recent activity