← previous blocknext block →recent activity
Analyzing
Block #98,664,230
25 transactions · 23 stateful · 2026-08-24 04:31:16 UTC
Parallelism
80/100
Blocked
39%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,664,230 · 25 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
2w04w15w010w111w012w113w214w315w417w223w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49fbc592…96ff
0xa6afd3…d132
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x2a9e9bd1…5368
0x2a68ba…90c5
10 touches
10 conflicts
0x11b69a7e…334e
0xee8c0e…1242
10 touches
10 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x0bd5c557…de1e
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
10 conflicts on slot 0x49fbc5927c…9596ff
Audit this contract →
← previous block·next block →recent activity