← previous blocknext block →recent activity
Analyzing
Block #100,229,571
108 transactions · 58 stateful · 2026-08-29 16:16:13 UTC
Parallelism
83/100
Blocked
78%
Avg conflicts / tx
1.83
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #100,229,571 · 108 txs across 18 waves · depth 18
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w09w110w111w213w114w043w353w256w157w259w360w461w562w663w764w865w966w1099w3100w6106w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b2b2e85…7bb1
0xd32edf…ff58
23 touches
66 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x97e4c862…4419
0x34b655…2a6f
18 touches
36 conflicts
0x00000000…00c9
0x34b655…2a6f
16 touches
28 conflicts
0xca841faa…486a
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0x261cbea7…e35d
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 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
66 conflicts on slot 0x0b2b2e859a…bf7bb1
Audit this contract →
← previous block·next block →recent activity