← previous blocknext block →recent activity
Analyzing
Block #98,014,492
32 transactions · 23 stateful · 2026-08-21 21:30:58 UTC
Parallelism
88/100
Blocked
48%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,014,492 · 32 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w111w012w113w014w015w119w221w322w023w225w326w128w130w231w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x354e383e…817c
0xa6afd3…d132
8 touches
6 conflicts
0x9d929e0c…9421
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xb31eb7d3…64eb
0xa6afd3…d132
6 touches
3 conflicts
0xb5c4826d…bdd6
0x2b46c0…1669
4 touches
1 conflict
0xdb067026…9eb8
0x2b46c0…1669
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x5ea8c657…71b9
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
6 conflicts on slot 0x354e383ef8…eb817c
Audit this contract →
← previous block·next block →recent activity