← previous blocknext block →recent activity
Analyzing
Block #98,490,063
76 transactions · 56 stateful · 2026-08-23 13:24:55 UTC
Parallelism
67/100
Blocked
68%
Avg conflicts / tx
2.83
Longest chain
25 deep
Execution timeline
did this block parallelize well?
view
block #98,490,063 · 76 txs across 25 waves · depth 25
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
wave w21
wave w22
wave w23
wave w24
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w738w839w940w1041w1150w1253w1556w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x218f6dfd…d1d9
0xd32edf…ff58
29 touches
105 conflicts
0x00000000…0012
0x1b6862…e19c
20 touches
45 conflicts
0x00000000…0013
0x1b6862…e19c
20 touches
45 conflicts
0x00000000…0015
0x1b6862…e19c
20 touches
45 conflicts
0x00000000…001c
0x1b6862…e19c
20 touches
45 conflicts
0x00000000…002c
0x1b6862…e19c
20 touches
45 conflicts
0x17a7f697…dcb5
0x1b6862…e19c
20 touches
45 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
20 touches
45 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
105 conflicts on slot 0x218f6dfde6…93d1d9
Audit this contract →
← previous block·next block →recent activity