← previous blocknext block →recent activity
Analyzing
Block #86,733,734
14 transactions · 11 stateful · 2026-07-10 00:48:04 UTC
Parallelism
86/100
Blocked
9%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,733,734 · 14 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
3w05w07w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3eedc44…373f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xacb691b6…8e39
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0x1f22e688…aed6
0x34b655…2a6f
2 touches
0 conflicts
0x40c0a898…eff9
0x34b655…2a6f
2 touches
0 conflicts
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 0xc3eedc448d…c6373f
Audit this contract →
← previous block·next block →recent activity