← previous blocknext block →recent activity
Analyzing
Block #98,752,172
20 transactions · 16 stateful · 2026-08-24 11:59:29 UTC
Parallelism
75/100
Blocked
56%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,752,172 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w07w28w29w210w316w418w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6518075e…2b17
0x2a68ba…90c5
8 touches
6 conflicts
0xabd5b1b6…9a8c
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x81716ce9…095f
0x34b655…2a6f
6 touches
3 conflicts
0x6eff310a…c34c
0x2b46c0…1669
4 touches
1 conflict
0xdeed550b…338b
0x2b46c0…1669
4 touches
1 conflict
0xe49b1b9b…0be1
0x2b46c0…1669
4 touches
1 conflict
0x382434ca…96b5
0x34b655…2a6f
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
6 conflicts on slot 0x6518075e89…5f2b17
Audit this contract →
← previous block·next block →recent activity