← previous blocknext block →recent activity
Analyzing
Block #86,104,087
25 transactions · 20 stateful · 2026-07-07 02:39:18 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.32
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,104,087 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w07w08w19w218w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18cf3003…51d1
0x065c9d…c394
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x7d42dc8b…fdb6
0x2a68ba…90c5
4 touches
1 conflict
0xa17960fc…f401
0x065c9d…c394
3 touches
1 conflict
0x1c0d7399…a20e
0xd32edf…ff58
3 touches
1 conflict
0xdd70bea3…1ffe
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0000
0x659bd0…a9da
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 0x18cf3003ed…9951d1
Audit this contract →
← previous block·next block →recent activity