← previous blocknext block →recent activity
Analyzing
Block #97,494,406
20 transactions · 16 stateful · 2026-08-20 01:27:01 UTC
Parallelism
75/100
Blocked
56%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,494,406 · 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
1w02w13w05w16w010w211w212w315w416w317w419w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0778475b…bd75
0x2a68ba…90c5
6 touches
3 conflicts
0xda1f3e2c…b73d
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xe56e2000…2e88
0x065c9d…c394
5 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0x511f46a7…eda8
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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 0x0778475bb2…63bd75
Audit this contract →
← previous block·next block →recent activity