← previous blocknext block →recent activity
Analyzing
Block #74,258,094
22 transactions · 17 stateful · 2026-05-13 05:34:35 UTC
Parallelism
73/100
Blocked
47%
Avg conflicts / tx
0.64
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #74,258,094 · 22 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
1w02w14w27w311w413w114w415w518w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b2bb5c4…c358
0xd32edf…ff58
7 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0xdd70bea3…1ffe
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0xc6a8c250…7379
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
6 conflicts on slot 0x0b2bb5c46b…83c358
Audit this contract →
← previous block·next block →recent activity