← previous blocknext block →recent activity
Analyzing
Block #71,045,178
23 transactions · 20 stateful · 2026-04-28 08:33:35 UTC
Parallelism
74/100
Blocked
50%
Avg conflicts / tx
0.78
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #71,045,178 · 23 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
1w02w13w24w35w47w08w19w011w413w518w119w020w021w122w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba49cb1e…3ccf
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x96a02dd2…10c1
0x065c9d…c394
4 touches
1 conflict
0x9afef26e…8ccb
0x065c9d…c394
4 touches
1 conflict
0x9f1a3707…b515
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
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
10 conflicts on slot 0xba49cb1e46…043ccf
Audit this contract →
← previous block·next block →recent activity