← previous blocknext block →recent activity
Analyzing
Block #106,283,123
30 transactions · 29 stateful · 2026-09-19 21:22:00 UTC
Parallelism
83/100
Blocked
48%
Avg conflicts / tx
1.23
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,283,123 · 30 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w07w18w29w310w011w112w213w315w424w225w326w428w129w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0x5164ab0e…01e1
0xc8689a…ee79
8 touches
6 conflicts
0xcc8faac2…c766
0x065c9d…c394
8 touches
6 conflicts
0x75f928fc…0465
0x34b655…2a6f
8 touches
6 conflicts
0x85a88798…f85e
0x34b655…2a6f
8 touches
6 conflicts
0x9a291a56…9a9c
0x34b655…2a6f
8 touches
6 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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity