← previous blocknext block →recent activity
Analyzing
Block #86,850,311
28 transactions · 19 stateful · 2026-07-10 13:47:06 UTC
Parallelism
82/100
Blocked
53%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,850,311 · 28 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
1w03w14w27w08w19w214w216w220w121w326w327w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec7fe04a…3c56
0x34b655…2a6f
8 touches
6 conflicts
0x2c390858…b1ed
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x273eabee…549e
0x34b655…2a6f
6 touches
3 conflicts
0x17c44db3…8888
0xa6afd3…d132
6 touches
3 conflicts
0x8d888c90…5479
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x93afca4c…b47b
0x1b6862…e19c
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
6 conflicts on slot 0xec7fe04ad1…2d3c56
Audit this contract →
← previous block·next block →recent activity