← previous blocknext block →recent activity
Analyzing
Block #98,014,029
31 transactions · 24 stateful · 2026-08-21 21:28:38 UTC
Parallelism
84/100
Blocked
42%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,014,029 · 31 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
2w04w06w07w110w012w114w215w218w119w322w325w427w028w130w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x354e383e…817c
0xa6afd3…d132
8 touches
6 conflicts
0xb31eb7d3…64eb
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xac1ad73d…be7c
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
6 touches
3 conflicts
0x9885a25f…2929
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 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
6 conflicts on slot 0x354e383ef8…eb817c
Audit this contract →
← previous block·next block →recent activity