← previous blocknext block →recent activity
Analyzing
Block #86,385,570
20 transactions · 17 stateful · 2026-07-08 09:59:06 UTC
Parallelism
85/100
Blocked
12%
Avg conflicts / tx
0.15
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,385,570 · 20 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
1w07w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x31324e52…bfe1
0x065c9d…c394
4 touches
1 conflict
0x49cbdb1b…bda4
0x065c9d…c394
4 touches
1 conflict
0x18cbdde0…84d1
0x065c9d…c394
2 touches
0 conflicts
0x29395979…5c3d
0x065c9d…c394
2 touches
0 conflicts
0x34103504…f5b7
0x065c9d…c394
2 touches
0 conflicts
0x489cb750…7069
0x065c9d…c394
2 touches
0 conflicts
0x5e5157c2…f848
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