← previous blocknext block →recent activity
Analyzing
Block #86,288,224
10 transactions · 8 stateful · 2026-07-07 23:08:42 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,288,224 · 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d6b9af1…9a38
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0efc210e…70ab
0x34b655…2a6f
2 touches
0 conflicts
0x2f00a9b1…bbb2
0x34b655…2a6f
2 touches
0 conflicts
0x303ffe31…18d3
0x34b655…2a6f
2 touches
0 conflicts
0x44ffddb7…bd70
0x34b655…2a6f
2 touches
0 conflicts
0x503d17fc…e0a9
0x34b655…2a6f
2 touches
0 conflicts
0x55c0b2db…4f66
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 0x7d6b9af162…f89a38
Audit this contract →
← previous block·next block →recent activity