← previous blocknext block →recent activity
Analyzing
Block #99,989,928
20 transactions · 18 stateful · 2026-08-28 20:09:40 UTC
Parallelism
55/100
Blocked
72%
Avg conflicts / tx
2
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #99,989,928 · 20 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w615w716w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x892daf6e…48d8
0x065c9d…c394
14 touches
21 conflicts
0x889d5e90…929a
0x2a68ba…90c5
14 touches
21 conflicts
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0x06e40499…165e
0x2b46c0…1669
10 touches
10 conflicts
0xa605468c…1bfc
0x2b46c0…1669
10 touches
10 conflicts
0xbb97db90…4c93
0xc8689a…ee79
10 touches
10 conflicts
0x8488f10f…9354
0x2b46c0…1669
6 touches
3 conflicts
0xc20bd100…8b0e
0x2b46c0…1669
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
21 conflicts on slot 0x892daf6e5d…6d48d8
Audit this contract →
← previous block·next block →recent activity