← previous blocknext block →recent activity
Analyzing
Block #74,761,041
44 transactions · 26 stateful · 2026-05-15 13:31:59 UTC
Parallelism
89/100
Blocked
35%
Avg conflicts / tx
0.41
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,761,041 · 44 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w08w112w016w117w228w029w132w033w134w235w336w440w041w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe0180fe…3ba5
0xd32edf…ff58
9 touches
10 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x00000000…0002
0xab3526…fa38
6 touches
3 conflicts
0x56a919c4…ab49
0xee8c0e…1242
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb82
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
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 0xfe0180fe87…bf3ba5
Audit this contract →
← previous block·next block →recent activity