← previous blocknext block →recent activity
Analyzing
Block #98,423,901
27 transactions · 23 stateful · 2026-08-23 07:51:42 UTC
Parallelism
78/100
Blocked
57%
Avg conflicts / tx
1.04
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,423,901 · 27 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
1w02w14w27w18w311w012w114w015w116w317w418w020w521w123w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x168ca7f5…2ea9
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
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
15 conflicts on slot 0x168ca7f54d…912ea9
Audit this contract →
← previous block·next block →recent activity