← previous blocknext block →recent activity
Analyzing
Block #98,021,022
30 transactions · 23 stateful · 2026-08-21 22:03:52 UTC
Parallelism
80/100
Blocked
48%
Avg conflicts / tx
0.6
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,021,022 · 30 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
1w02w13w26w07w08w110w017w118w219w320w322w423w424w529w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7df61af2…ebea
0xd32edf…ff58
9 touches
10 conflicts
0x581b829b…9578
0x34b655…2a6f
4 touches
1 conflict
0xbaf77397…e798
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xbb3f3c…e046
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x04994ed2…9032
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: FastLane: FastLaneAuctionHandler
10 conflicts on slot 0x7df61af25a…a9ebea
Audit this contract →
← previous block·next block →recent activity