← previous blocknext block →recent activity
Analyzing
Block #76,234,961
19 transactions · 14 stateful · 2026-05-22 09:35:24 UTC
Parallelism
74/100
Blocked
36%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,234,961 · 19 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
1w02w13w24w35w46w08w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x861ec84a…6163
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0xfe2bac2b…2cec
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0x78694995…f66e
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 0x861ec84a17…df6163
Audit this contract →
← previous block·next block →recent activity