← previous blocknext block →recent activity
Analyzing
Block #98,334,519
25 transactions · 24 stateful · 2026-08-23 00:22:01 UTC
Parallelism
64/100
Blocked
63%
Avg conflicts / tx
1.64
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #98,334,519 · 25 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w08w111w412w215w516w617w520w624w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf004586a…128e
0xd32edf…ff58
13 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0019
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0029
0x1b6862…e19c
8 touches
6 conflicts
0xba5743c7…21c0
0x1b6862…e19c
8 touches
6 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
21 conflicts on slot 0xf004586a2a…e7128e
Audit this contract →
← previous block·next block →recent activity