← previous blocknext block →recent activity
Analyzing
Block #86,904,236
11 transactions · 10 stateful · 2026-07-10 19:47:44 UTC
Parallelism
82/100
Blocked
10%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,904,236 · 11 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
6w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x37ee30c9…9e70
0x34b655…2a6f
4 touches
1 conflict
0xd5c56995…6d22
0x34b655…2a6f
4 touches
1 conflict
0x8e2e1cc1…9f77
0x34b655…2a6f
4 touches
1 conflict
0xa1940963…fe97
0x34b655…2a6f
4 touches
1 conflict
0xc1251c8d…2b25
0x34b655…2a6f
4 touches
1 conflict
0xd5c56995…6d21
0x34b655…2a6f
4 touches
1 conflict
0x5ad391be…e03b
0x34b655…2a6f
3 touches
1 conflict
0x727fbce7…0c80
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 0x37ee30c996…d19e70
Audit this contract →
← previous block·next block →recent activity