← previous blocknext block →recent activity
Analyzing
Block #106,047,214
25 transactions · 24 stateful · 2026-09-19 01:34:40 UTC
Parallelism
64/100
Blocked
71%
Avg conflicts / tx
2.16
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,047,214 · 25 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
1w02w13w24w35w46w57w68w715w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x906f18f2…858b
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x65bd5770…5ecd
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00d80212…7897
0x73ca90…1130
10 touches
10 conflicts
0x00d80212…7898
0x73ca90…1130
10 touches
10 conflicts
0x063037c7…55f7
0x6f6493…b480
9 touches
10 conflicts
0x09bdf82f…e468
0x6f6493…b480
9 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
36 conflicts on slot 0x906f18f2b0…f8858b
Audit this contract →
← previous block·next block →recent activity