← previous blocknext block →recent activity
Analyzing
Block #98,058,967
23 transactions · 23 stateful · 2026-08-22 01:14:55 UTC
Parallelism
78/100
Blocked
39%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,058,967 · 23 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
1w02w13w06w07w111w212w013w315w217w318w420w021w322w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf88ccd07…a684
0xa6afd3…d132
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x2bd1c200…56de
0x34b655…2a6f
6 touches
3 conflicts
0xadbda1a7…5f21
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xdb95e18e…c73b
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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
10 conflicts on slot 0xf88ccd07d5…f2a684
Audit this contract →
← previous block·next block →recent activity