← previous blocknext block →recent activity
Analyzing
Block #86,181,472
48 transactions · 33 stateful · 2026-07-07 11:15:52 UTC
Parallelism
88/100
Blocked
39%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,181,472 · 48 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w06w17w08w010w112w013w114w215w318w019w238w439w543w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18cf3003…51d1
0x065c9d…c394
10 touches
10 conflicts
0x6b19e552…ed64
0xd32edf…ff58
9 touches
10 conflicts
0xc3c8642a…7da5
0x2a68ba…90c5
6 touches
3 conflicts
0xcc8faac2…c766
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0xcb45d9d6…cb86
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 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
10 conflicts on slot 0x18cf3003ed…9951d1
Audit this contract →
← previous block·next block →recent activity