← previous blocknext block →recent activity
Analyzing
Block #97,356,818
37 transactions · 26 stateful · 2026-08-19 13:30:10 UTC
Parallelism
78/100
Blocked
58%
Avg conflicts / tx
1.24
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #97,356,818 · 37 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w36w413w514w615w516w625w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x97987932…2a28
0xd32edf…ff58
15 touches
28 conflicts
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0xba5743c7…21c5
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 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
28 conflicts on slot 0x979879321d…3d2a28
Audit this contract →
← previous block·next block →recent activity