← previous blocknext block →recent activity
Analyzing
Block #98,365,246
25 transactions · 22 stateful · 2026-08-23 02:56:35 UTC
Parallelism
84/100
Blocked
27%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,365,246 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w28w211w012w117w323w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc26cdcb2…dd2b
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0x3a3097d7…2ab4
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
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 0xc26cdcb299…a7dd2b
Audit this contract →
← previous block·next block →recent activity