← previous blocknext block →recent activity
Analyzing
Block #98,264,403
21 transactions · 20 stateful · 2026-08-22 18:29:13 UTC
Parallelism
76/100
Blocked
45%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,264,403 · 21 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
1w02w13w05w08w09w110w211w312w213w314w417w120w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3c30e1da…508b
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0028
0x1b6862…e19c
6 touches
3 conflicts
0xba5743c7…21bf
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
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: FastLane: FastLaneAuctionHandler
6 conflicts on slot 0x3c30e1da8f…b7508b
Audit this contract →
← previous block·next block →recent activity