← previous blocknext block →recent activity
Analyzing
Block #86,741,535
17 transactions · 13 stateful · 2026-07-10 01:40:14 UTC
Parallelism
76/100
Blocked
23%
Avg conflicts / tx
0.24
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,741,535 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0xe60e9000…c058
0x34b655…2a6f
4 touches
1 conflict
0xf0ad9713…5796
0x34b655…2a6f
4 touches
1 conflict
0x0a5c34c6…324d
0x34b655…2a6f
4 touches
1 conflict
0x0c15f714…46ab
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5d863b2f…bd28
0x34b655…2a6f
4 touches
1 conflict
0x63ef3eae…b1ea
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
3 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity