← previous blocknext block →recent activity
Analyzing
Block #98,749,614
33 transactions · 25 stateful · 2026-08-24 11:46:35 UTC
Parallelism
79/100
Blocked
48%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #98,749,614 · 33 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
1w03w14w28w310w411w013w515w116w220w421w524w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3d00a256…1c01
0xd32edf…ff58
13 touches
21 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0x6aa624fd…a84c
0x1b6862…e19c
4 touches
1 conflict
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 0x3d00a25647…1b1c01
Audit this contract →
← previous block·next block →recent activity