← previous blocknext block →recent activity
Analyzing
Block #86,358,161
17 transactions · 15 stateful · 2026-07-08 06:55:49 UTC
Parallelism
82/100
Blocked
20%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,358,161 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w18w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x49cbdb1b…bda4
0x065c9d…c394
4 touches
1 conflict
0x27a04273…27c5
0x065c9d…c394
2 touches
0 conflicts
0x2b235d67…9ecb
0x065c9d…c394
2 touches
0 conflicts
0x4c69f230…6fa2
0x065c9d…c394
2 touches
0 conflicts
0x5ad8b548…6f3a
0x065c9d…c394
2 touches
0 conflicts
0x670ea525…1a7d
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity