← previous blocknext block →recent activity
Analyzing
Block #98,747,261
19 transactions · 19 stateful · 2026-08-24 11:34:45 UTC
Parallelism
68/100
Blocked
47%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,747,261 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w08w010w411w512w115w116w218w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5a16ccc…62d1
0xd32edf…ff58
11 touches
15 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb4c703ab…f8cf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x46cb45de…a566
0x188d58…ea8e
2 touches
0 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
15 conflicts on slot 0xa5a16ccc58…da62d1
Audit this contract →
← previous block·next block →recent activity