← previous blocknext block →recent activity
Analyzing
Block #106,014,748
19 transactions · 15 stateful · 2026-09-18 22:51:17 UTC
Parallelism
68/100
Blocked
60%
Avg conflicts / tx
1.11
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,014,748 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w18w211w513w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4b6bdf00…0535
0xd32edf…ff58
11 touches
15 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
6 touches
3 conflicts
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
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
15 conflicts on slot 0x4b6bdf0025…af0535
Audit this contract →
← previous block·next block →recent activity