← previous blocknext block →recent activity
Analyzing
Block #98,841,130
33 transactions · 29 stateful · 2026-08-24 19:27:22 UTC
Parallelism
85/100
Blocked
41%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,841,130 · 33 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
1w02w13w25w06w17w19w215w316w320w421w322w423w432w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8498c683…50c2
0xd32edf…ff58
9 touches
10 conflicts
0x8e66da19…66b6
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…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x6b1259e6…4e10
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 0x8498c68341…a250c2
Audit this contract →
← previous block·next block →recent activity