← previous blocknext block →recent activity
Analyzing
Block #98,533,531
20 transactions · 18 stateful · 2026-08-23 17:10:04 UTC
Parallelism
70/100
Blocked
39%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,533,531 · 20 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
1w03w14w25w311w412w513w014w015w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7fb22da5…af8f
0xd32edf…ff58
11 touches
15 conflicts
0x706c758c…2fdb
0x34b655…2a6f
4 touches
1 conflict
0x0a9de7e4…b2e4
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x917ce24b…090d
0x34b655…2a6f
4 touches
1 conflict
0xaceaf2ae…52e8
0x34b655…2a6f
4 touches
1 conflict
0xb2fe971d…5165
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
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
15 conflicts on slot 0x7fb22da526…51af8f
Audit this contract →
← previous block·next block →recent activity