← previous blocknext block →recent activity
Analyzing
Block #106,540,665
36 transactions · 29 stateful · 2026-09-20 18:58:10 UTC
Parallelism
72/100
Blocked
55%
Avg conflicts / tx
1.42
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,540,665 · 36 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w39w410w512w620w124w727w831w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
16 touches
28 conflicts
0xaad6be10…0801
0x2a68ba…90c5
14 touches
21 conflicts
0x18cf3003…51d1
0x065c9d…c394
14 touches
21 conflicts
0xcc8faac2…c766
0x065c9d…c394
12 touches
15 conflicts
0xb686e6f5…f6d1
0xc8689a…ee79
10 touches
10 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
10 touches
10 conflicts
0x06e40499…165e
0x34ae4d…3fc5
10 touches
10 conflicts
0xa605468c…1bfc
0x34ae4d…3fc5
10 touches
10 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
28 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity