← previous blocknext block →recent activity
Analyzing
Block #99,975,407
39 transactions · 31 stateful · 2026-08-28 18:56:30 UTC
Parallelism
74/100
Blocked
58%
Avg conflicts / tx
1.56
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #99,975,407 · 39 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
1w02w16w07w28w310w412w513w614w716w127w729w831w132w937w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
16 touches
28 conflicts
0x5f77d607…2c84
0x065c9d…c394
14 touches
21 conflicts
0x31447240…5797
0xd32edf…ff58
13 touches
21 conflicts
0x892daf6e…48d8
0x065c9d…c394
12 touches
15 conflicts
0x00000000…001a
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002a
0x1b6862…e19c
10 touches
10 conflicts
0xc2aacf41…54ff
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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