← previous blocknext block →recent activity
Analyzing
Block #86,531,215
14 transactions · 11 stateful · 2026-07-09 02:12:05 UTC
Parallelism
86/100
Blocked
18%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,531,215 · 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
3w05w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xda2ee2e7…968a
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x0bae7acf…27ab
0x34b655…2a6f
2 touches
0 conflicts
0x1e88119b…2ba4
0x34b655…2a6f
2 touches
0 conflicts
0x26186ace…4f57
0x34b655…2a6f
2 touches
0 conflicts
0x28f40bdb…42f9
0x34b655…2a6f
2 touches
0 conflicts
0x508f9ae2…6bcf
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: Kuru Exchange: Market-MON/USDC
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity