← previous blocknext block →recent activity
Analyzing
Block #98,429,174
14 transactions · 13 stateful · 2026-08-23 08:18:13 UTC
Parallelism
57/100
Blocked
38%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,429,174 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w18w29w311w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x4ca87477…f8da
0xa6afd3…d132
8 touches
6 conflicts
0xf12a8246…e00f
0xa6afd3…d132
6 touches
3 conflicts
0xd3e34854…ba6f
0xa6afd3…d132
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x4d65d4cc…2261
0xa6afd3…d132
3 touches
1 conflict
0x4f0309e6…3365
0xa6afd3…d132
3 touches
1 conflict
0xf1fbcd40…9515
0x2b46c0…1669
2 touches
0 conflicts
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity