← previous blocknext block →recent activity
Analyzing
Block #106,014,398
36 transactions · 25 stateful · 2026-09-18 22:49:32 UTC
Parallelism
83/100
Blocked
72%
Avg conflicts / tx
1.47
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,014,398 · 36 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
2w05w06w17w28w311w414w424w128w529w430w531w532w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18cf3003…51d1
0x065c9d…c394
12 touches
15 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0xaad6be10…0801
0x2a68ba…90c5
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0x32c9c873…604c
0x34b655…2a6f
8 touches
6 conflicts
0x3f152ba8…cea6
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
15 conflicts on slot 0x18cf3003ed…9951d1
Audit this contract →
← previous block·next block →recent activity