← previous blocknext block →recent activity
Analyzing
Block #100,119,085
36 transactions · 33 stateful · 2026-08-29 06:59:54 UTC
Parallelism
75/100
Blocked
73%
Avg conflicts / tx
2.39
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #100,119,085 · 36 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w510w612w113w715w817w329w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36b70c71…5058
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…0002
0xf5b5f7…6d70
16 touches
28 conflicts
0x00000000…0012
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…001d
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…002d
0x1b6862…e19c
16 touches
28 conflicts
0x17a7f697…dcb6
0x1b6862…e19c
16 touches
28 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
36 conflicts on slot 0x36b70c718a…af5058
Audit this contract →
← previous block·next block →recent activity