← previous blocknext block →recent activity
Analyzing
Block #98,016,347
21 transactions · 21 stateful · 2026-08-21 21:40:18 UTC
Parallelism
76/100
Blocked
57%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,016,347 · 21 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
1w02w13w24w35w06w17w08w19w010w111w413w414w215w016w117w018w120w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f30ae8e…d82d
0xd32edf…ff58
9 touches
10 conflicts
0xe75ce681…ba60
0x188d58…ea8e
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…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x98067f20…59e6
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 0x6f30ae8e34…d2d82d
Audit this contract →
← previous block·next block →recent activity