← previous blocknext block →recent activity
Analyzing
Block #98,460,000
30 transactions · 26 stateful · 2026-08-23 10:53:31 UTC
Parallelism
80/100
Blocked
42%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,460,000 · 30 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
1w02w13w24w35w48w09w010w011w112w018w119w221w122w223w124w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6140b94…eb3f
0xd32edf…ff58
9 touches
10 conflicts
0xa56ae218…1fc5
0x34b655…2a6f
6 touches
3 conflicts
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…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x91220b8f…7a05
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 0xc6140b9446…18eb3f
Audit this contract →
← previous block·next block →recent activity