← previous blocknext block →recent activity
Analyzing
Block #99,172,530
13 transactions · 13 stateful · 2026-08-25 23:21:22 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,172,530 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w17w311w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x06ce5d4b…c122
0x2b46c0…1669
4 touches
1 conflict
0x213ee207…a151
0x2b46c0…1669
4 touches
1 conflict
0x2f74f175…9284
0x2b46c0…1669
4 touches
1 conflict
0x2f74f175…9285
0x2b46c0…1669
4 touches
1 conflict
0x2f74f175…9288
0x2b46c0…1669
4 touches
1 conflict
0x2f74f175…9289
0x2b46c0…1669
4 touches
1 conflict
0x53e50026…6d8c
0x2b46c0…1669
4 touches
1 conflict
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
3 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity