← previous blocknext block →recent activity
Analyzing
Block #98,445,114
30 transactions · 21 stateful · 2026-08-23 09:38:24 UTC
Parallelism
73/100
Blocked
57%
Avg conflicts / tx
0.93
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #98,445,114 · 30 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
1w02w13w24w35w46w112w513w618w722w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf83fdca3…3393
0xd32edf…ff58
11 touches
15 conflicts
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0xd66e6e81…05b0
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
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 0xf83fdca33a…fe3393
Audit this contract →
← previous block·next block →recent activity