← previous blocknext block →recent activity
Analyzing
Block #97,990,819
23 transactions · 19 stateful · 2026-08-21 19:31:35 UTC
Parallelism
87/100
Blocked
32%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,990,819 · 23 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w09w010w111w216w118w019w122w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36c01dd3…5ea6
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
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
3 conflicts on slot 0x36c01dd310…b65ea6
Audit this contract →
← previous block·next block →recent activity