← previous blocknext block →recent activity
Analyzing
Block #97,991,066
19 transactions · 19 stateful · 2026-08-21 19:32:50 UTC
Parallelism
79/100
Blocked
37%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,991,066 · 19 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
1w02w03w14w15w26w37w09w010w111w218w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x2b199048…6980
0xd32edf…ff58
5 touches
3 conflicts
0xff2d7c99…ab81
0x065c9d…c394
5 touches
3 conflicts
0xd5b10148…e633
0x1b6862…e19c
4 touches
1 conflict
0x3e49348b…9445
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x5164ab0e…01e1
0xc8689a…ee79
4 touches
1 conflict
0xbb97db90…4c93
0xc8689a…ee79
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