← previous blocknext block →recent activity
Analyzing
Block #86,803,226
14 transactions · 12 stateful · 2026-07-10 08:32:14 UTC
Parallelism
64/100
Blocked
50%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,803,226 · 14 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
1w04w05w16w27w38w19w413w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2264392…d5f4
0x34b655…2a6f
10 touches
10 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xf7ab945c…597e
0x34b655…2a6f
6 touches
3 conflicts
0x26054cbe…47df
0x34b655…2a6f
6 touches
3 conflicts
0x7efa41dd…b220
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
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
10 conflicts on slot 0xe2264392ec…c0d5f4
Audit this contract →
← previous block·next block →recent activity