← previous blocknext block →recent activity
Analyzing
Block #99,082,666
35 transactions · 25 stateful · 2026-08-25 15:49:01 UTC
Parallelism
80/100
Blocked
40%
Avg conflicts / tx
0.86
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,082,666 · 35 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w07w18w19w210w312w015w319w126w427w528w630w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
12 touches
15 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x47b807a2…3307
0x065c9d…c394
8 touches
6 conflicts
0x11258774…9892
0x2a68ba…90c5
6 touches
3 conflicts
0xbb97db90…4c93
0xc8689a…ee79
6 touches
3 conflicts
0x41755291…977f
0x065c9d…c394
6 touches
3 conflicts
0xf020add3…a6a9
0x065c9d…c394
5 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: MarginAccount
15 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity