← previous blocknext block →recent activity
Analyzing
Block #106,786,711
30 transactions · 29 stateful · 2026-09-21 15:37:29 UTC
Parallelism
67/100
Blocked
59%
Avg conflicts / tx
1.63
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,786,711 · 30 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w07w19w211w112w213w314w419w320w422w526w627w728w829w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0xdfa159d0…1576
0x065c9d…c394
10 touches
10 conflicts
0xcc4f1f14…aa5f
0x065c9d…c394
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xb7b446d2…2006
0x34b655…2a6f
8 touches
6 conflicts
0x21d22421…0b7a
0x34b655…2a6f
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
15 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity