← previous blocknext block →recent activity
Analyzing
Block #106,576,527
16 transactions · 16 stateful · 2026-09-20 21:58:39 UTC
Parallelism
81/100
Blocked
19%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,576,527 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w114w015w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x17c93766…889e
0x34b655…2a6f
2 touches
0 conflicts
0x32b8cbe7…8bac
0x34b655…2a6f
2 touches
0 conflicts
0x36223362…c0ce
0x34b655…2a6f
2 touches
0 conflicts
0x61af24a0…d4bc
0x34b655…2a6f
2 touches
0 conflicts
0x7e5ea60a…c4a4
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity