← previous blocknext block →recent activity
Analyzing
Block #76,115,234
24 transactions · 20 stateful · 2026-05-21 20:17:54 UTC
Parallelism
71/100
Blocked
40%
Avg conflicts / tx
0.96
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #76,115,234 · 24 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
1w02w13w24w35w47w510w111w014w615w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6650f0f1…2483
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0003
0xd004cf…da29
4 touches
1 conflict
0xdbde8233…3e76
0xdb8585…7777
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0x45364cf9…65d6
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
21 conflicts on slot 0x6650f0f184…7e2483
Audit this contract →
← previous block·next block →recent activity