← previous blocknext block →recent activity
Analyzing
Block #98,072,028
35 transactions · 31 stateful · 2026-08-22 02:20:38 UTC
Parallelism
71/100
Blocked
68%
Avg conflicts / tx
1.83
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #98,072,028 · 35 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w515w119w621w723w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xed9b6cc9…df7d
0xd32edf…ff58
17 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…002c
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001c
0x1b6862…e19c
10 touches
10 conflicts
0xe5060fe3…ebe7
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 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
36 conflicts on slot 0xed9b6cc9ea…90df7d
Audit this contract →
← previous block·next block →recent activity