← previous blocknext block →recent activity
Analyzing
Block #98,847,668
40 transactions · 33 stateful · 2026-08-24 20:00:15 UTC
Parallelism
77/100
Blocked
64%
Avg conflicts / tx
1.15
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #98,847,668 · 40 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
1w02w13w24w35w46w516w618w719w628w833w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x509f74e3…a265
0xd32edf…ff58
13 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
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
0x6aa624fd…a84e
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 0x509f74e32a…91a265
Audit this contract →
← previous block·next block →recent activity