← previous blocknext block →recent activity
Analyzing
Block #105,856,230
30 transactions · 26 stateful · 2026-09-18 09:32:25 UTC
Parallelism
80/100
Blocked
46%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,856,230 · 30 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
1w02w03w14w06w07w19w113w014w115w216w117w218w219w020w322w123w425w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x1e75075e…307f
0xd32edf…ff58
7 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x97e4c862…4419
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x49cbdb1b…bda4
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0xa4fd1b6f…d731
0x1b6862…e19c
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity