← previous blocknext block →recent activity
Analyzing
Block #99,160,345
22 transactions · 20 stateful · 2026-08-25 22:20:04 UTC
Parallelism
77/100
Blocked
40%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,160,345 · 22 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
1w04w15w06w17w28w011w012w313w414w115w017w018w120w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xb26ff3de…9352
0xa6afd3…d132
6 touches
3 conflicts
0x7ea1cfdf…81c0
0xa6afd3…d132
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xcc93d643…52ea
0xa6afd3…d132
5 touches
3 conflicts
0xf5e74967…55cb
0xa6afd3…d132
5 touches
3 conflicts
0xb05cd4f5…73d0
0x2b46c0…1669
4 touches
1 conflict
0xdb067026…9eb8
0x2b46c0…1669
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity