← previous blocknext block →recent activity
Analyzing
Block #108,674,217
25 transactions · 22 stateful · 2026-09-28 06:00:38 UTC
Parallelism
68/100
Blocked
68%
Avg conflicts / tx
1.68
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,674,217 · 25 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
1w02w13w24w35w46w57w69w613w718w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5f6684c…1bfb
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0012
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0018
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0051
0x1b6862…e19c
12 touches
15 conflicts
0x5c421c70…c2eb
0x1b6862…e19c
12 touches
15 conflicts
0xba5743c7…21bf
0x1b6862…e19c
12 touches
15 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
28 conflicts on slot 0xc5f6684cfb…731bfb
Audit this contract →
← previous block·next block →recent activity