← previous blocknext block →recent activity
Analyzing
Block #86,104,171
41 transactions · 26 stateful · 2026-07-07 02:39:51 UTC
Parallelism
85/100
Blocked
42%
Avg conflicts / tx
0.49
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,104,171 · 41 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
1w08w011w012w113w114w215w316w117w119w020w130w232w433w537w038w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18cf3003…51d1
0x065c9d…c394
8 touches
6 conflicts
0x604f07e2…e304
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb84
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
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
6 conflicts on slot 0x18cf3003ed…9951d1
Audit this contract →
← previous block·next block →recent activity