← previous blocknext block →recent activity
Analyzing
Block #98,081,098
40 transactions · 29 stateful · 2026-08-22 03:06:17 UTC
Parallelism
80/100
Blocked
45%
Avg conflicts / tx
0.88
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #98,081,098 · 40 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w39w425w526w527w628w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5805ffda…c1b8
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0xc13fac9b…d2d2
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0007
0x340143…768f
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
28 conflicts on slot 0x5805ffdaf2…e5c1b8
Audit this contract →
← previous block·next block →recent activity