← previous blocknext block →recent activity
Analyzing
Block #102,050,204
22 transactions · 19 stateful · 2026-09-05 01:06:13 UTC
Parallelism
55/100
Blocked
68%
Avg conflicts / tx
1.86
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #102,050,204 · 22 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
1w02w13w24w35w46w57w68w717w818w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0xaad6be10…0801
0x2a68ba…90c5
10 touches
10 conflicts
0x95523e2a…4c01
0x065c9d…c394
10 touches
10 conflicts
0xdb8288e3…7979
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x49a1b24e…cff9
0xd32edf…ff58
9 touches
10 conflicts
0xd25997d0…a686
0x1b6862…e19c
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity