← previous blocknext block →recent activity
Analyzing
Block #86,394,633
14 transactions · 13 stateful · 2026-07-08 10:59:38 UTC
Parallelism
86/100
Blocked
8%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,394,633 · 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x27a04273…27c5
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x103eb92a…a8e9
0x065c9d…c394
2 touches
0 conflicts
0x11803afb…56d3
0x065c9d…c394
2 touches
0 conflicts
0x21728e8b…2ab2
0x065c9d…c394
2 touches
0 conflicts
0x49cbdb1b…bda4
0x065c9d…c394
2 touches
0 conflicts
0x6b5cfb12…9b20
0x065c9d…c394
2 touches
0 conflicts
0x6f133a2e…90da
0x065c9d…c394
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 0x27a04273d4…7327c5
Audit this contract →
← previous block·next block →recent activity