← previous blocknext block →recent activity
Analyzing
Block #102,482,125
37 transactions · 29 stateful · 2026-09-06 13:35:05 UTC
Parallelism
78/100
Blocked
59%
Avg conflicts / tx
1.11
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #102,482,125 · 37 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w37w49w511w618w127w128w731w133w235w336w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0x5f77d607…2c84
0x065c9d…c394
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x892daf6e…48d8
0x065c9d…c394
8 touches
6 conflicts
0xb686e6f5…f6d1
0xc8689a…ee79
8 touches
6 conflicts
0xa605468c…1bfc
0x34ae4d…3fc5
8 touches
6 conflicts
0x00000000…002c
0x1b6862…e19c
6 touches
3 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