← previous blocknext block →recent activity
Analyzing
Block #97,852,340
30 transactions · 23 stateful · 2026-08-21 07:44:07 UTC
Parallelism
83/100
Blocked
48%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,852,340 · 30 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
2w03w14w05w16w27w39w010w116w217w318w419w220w321w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd4de6258…941f
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0002
0x103de0…bb55
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x305e45b5…fbdd
0xa6afd3…d132
4 touches
1 conflict
0x5e2bd0c1…7ca2
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
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 0xd4de62581c…f0941f
Audit this contract →
← previous block·next block →recent activity