← previous blocknext block →recent activity
Analyzing
Block #100,057,153
20 transactions · 19 stateful · 2026-08-29 01:48:04 UTC
Parallelism
70/100
Blocked
47%
Avg conflicts / tx
1.15
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,057,153 · 20 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
1w02w13w24w35w46w48w09w512w013w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x591b0387…4733
0xd32edf…ff58
11 touches
15 conflicts
0xead15497…1dbe
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x64e1f0ce…715a
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
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
15 conflicts on slot 0x591b038764…7b4733
Audit this contract →
← previous block·next block →recent activity