← previous blocknext block →recent activity
Analyzing
Block #106,336,268
12 transactions · 12 stateful · 2026-09-20 01:49:26 UTC
Parallelism
75/100
Blocked
25%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,336,268 · 12 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
2w03w17w08w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68397ef4…16f5
0x065c9d…c394
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x1e0d4936…bd3d
0x065c9d…c394
3 touches
1 conflict
0x993fef25…5138
0x065c9d…c394
3 touches
1 conflict
0xf2a24134…5c65
0x065c9d…c394
3 touches
1 conflict
0x4f858025…9e3e
0x065c9d…c394
3 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
1 conflict on slot 0x68397ef4ec…cf16f5
Audit this contract →
← previous block·next block →recent activity