← previous blocknext block →recent activity
Analyzing
Block #108,671,401
39 transactions · 32 stateful · 2026-09-28 05:46:27 UTC
Parallelism
64/100
Blocked
69%
Avg conflicts / tx
2.31
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #108,671,401 · 39 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w731w533w637w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6765d860…fbc0
0xd32edf…ff58
19 touches
45 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…0012
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0018
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0028
0x1b6862…e19c
16 touches
28 conflicts
0x6235638c…6436
0x1b6862…e19c
16 touches
28 conflicts
0xcb45d9d6…cb80
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
45 conflicts on slot 0x6765d86080…d3fbc0
Audit this contract →
← previous block·next block →recent activity