← previous blocknext block →recent activity
Analyzing
Block #99,083,501
24 transactions · 17 stateful · 2026-08-25 15:53:14 UTC
Parallelism
67/100
Blocked
65%
Avg conflicts / tx
0.88
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #99,083,501 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w27w39w010w413w515w116w217w618w722w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xb55f6c75…c2d2
0xa6afd3…d132
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x9d929e0c…9421
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0x98067f20…59e3
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
6 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity