← previous blocknext block →recent activity
Analyzing
Block #98,384,440
17 transactions · 16 stateful · 2026-08-23 04:33:09 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,384,440 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w18w19w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa32f1ceb…2ab5
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0xced2f4ba…f03b
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x485d2778…aa5c
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
10 conflicts on slot 0xa32f1ceb39…7c2ab5
Audit this contract →
← previous block·next block →recent activity