← previous blocknext block →recent activity
Analyzing
Block #98,095,650
24 transactions · 21 stateful · 2026-08-22 04:19:30 UTC
Parallelism
88/100
Blocked
38%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,095,650 · 24 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w05w111w012w114w116w117w118w222w223w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xadce6355…03bf
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x3ad04ce1…1904
0xa6afd3…d132
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2827ae77…4368
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: Market-WETH/USDC
1 conflict on slot 0xadce6355bf…bc03bf
Audit this contract →
← previous block·next block →recent activity