← previous blocknext block →recent activity
Analyzing
Block #108,962,473
18 transactions · 18 stateful · 2026-09-29 06:15:52 UTC
Parallelism
50/100
Blocked
61%
Avg conflicts / tx
2.17
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #108,962,473 · 18 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
1w03w15w06w17w29w310w413w214w515w616w717w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05db7144…456c
0xd32edf…ff58
17 touches
36 conflicts
0x0f28fb99…3d2f
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001e
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002e
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0040
0x1b6862…e19c
8 touches
6 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 0x05db7144cd…03456c
Audit this contract →
← previous block·next block →recent activity