← previous blocknext block →recent activity
Analyzing
Block #86,807,461
13 transactions · 8 stateful · 2026-07-10 09:00:30 UTC
Parallelism
77/100
Blocked
38%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,807,461 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w211w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf95f86cd…e927
0x34b655…2a6f
4 touches
1 conflict
0x50d2128a…e53f
0x34b655…2a6f
4 touches
1 conflict
0x58f65aa1…8f98
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x8344e533…436c
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x9a287655…f785
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
1 conflict on slot 0xf95f86cd53…dfe927
Audit this contract →
← previous block·next block →recent activity