← previous blocknext block →recent activity
Analyzing
Block #106,958,618
27 transactions · 26 stateful · 2026-09-22 06:02:47 UTC
Parallelism
78/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,958,618 · 27 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
1w02w03w14w18w29w210w011w112w213w014w115w220w321w422w525w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0x95523e2a…4c01
0x065c9d…c394
8 touches
6 conflicts
0x77ed432f…fa04
0x065c9d…c394
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x125f12…a50b
6 touches
3 conflicts
0x95e04914…86fa
0x34b655…2a6f
6 touches
3 conflicts
0x839c0c71…bada
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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