← previous blocknext block →recent activity
Analyzing
Block #86,853,537
17 transactions · 16 stateful · 2026-07-10 14:08:40 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,853,537 · 17 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
6w07w010w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2ff6094d…ecb8
0x34b655…2a6f
4 touches
1 conflict
0x42ccc5f6…641e
0x34b655…2a6f
4 touches
1 conflict
0x44c93bf8…0a6b
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5d863b2f…bd28
0x34b655…2a6f
4 touches
1 conflict
0x608e3013…5f6a
0x34b655…2a6f
4 touches
1 conflict
0x62b13313…bbe8
0x34b655…2a6f
4 touches
1 conflict
0x699ee60f…de01
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 0x2ff6094da1…d7ecb8
Audit this contract →
← previous block·next block →recent activity