← previous blocknext block →recent activity
Analyzing
Block #98,425,900
30 transactions · 27 stateful · 2026-08-23 08:01:45 UTC
Parallelism
77/100
Blocked
44%
Avg conflicts / tx
1.03
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #98,425,900 · 30 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w28w010w111w214w215w316w417w519w628w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63219514…04e7
0xd32edf…ff58
13 touches
21 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x00000000…0002
0xbb3f3c…e046
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
6 touches
3 conflicts
0x928d6b23…5370
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
21 conflicts on slot 0x63219514e5…b804e7
Audit this contract →
← previous block·next block →recent activity