← previous blocknext block →recent activity
Analyzing
Block #98,930,294
25 transactions · 23 stateful · 2026-08-25 02:55:55 UTC
Parallelism
76/100
Blocked
61%
Avg conflicts / tx
1.28
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,930,294 · 25 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
1w02w13w24w15w26w08w09w110w211w313w314w415w417w524w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd0ff0700…fd27
0xd32edf…ff58
9 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
6 touches
3 conflicts
0x6aa624fd…a850
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
10 conflicts on slot 0xd0ff0700e1…8efd27
Audit this contract →
← previous block·next block →recent activity