← previous blocknext block →recent activity
Analyzing
Block #97,395,623
21 transactions · 21 stateful · 2026-08-19 17:07:58 UTC
Parallelism
76/100
Blocked
43%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,395,623 · 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
1w02w13w24w05w06w17w28w09w310w411w014w316w120w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3a106a5…571f
0xd32edf…ff58
9 touches
10 conflicts
0xec431e8f…8c4d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0x84611dd3…b347
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x05b1b07a…7a99
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
10 conflicts on slot 0xf3a106a559…e8571f
Audit this contract →
← previous block·next block →recent activity