← previous blocknext block →recent activity
Analyzing
Block #74,918,266
38 transactions · 28 stateful · 2026-05-16 07:01:10 UTC
Parallelism
82/100
Blocked
68%
Avg conflicts / tx
1.26
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #74,918,266 · 38 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w610w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c160076…a324
0xd32edf…ff58
13 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0x1f8a126c…9aa6
0x1b6862…e19c
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
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
21 conflicts on slot 0x1c16007655…68a324
Audit this contract →
← previous block·next block →recent activity