← previous blocknext block →recent activity
Analyzing
Block #76,576,822
28 transactions · 22 stateful · 2026-05-23 23:31:28 UTC
Parallelism
79/100
Blocked
41%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #76,576,822 · 28 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
1w02w13w24w38w011w112w414w416w525w026w127w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfa159d0…1576
0x065c9d…c394
8 touches
6 conflicts
0xc2a5ddf1…dc99
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0x5a3732cb…edb2
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
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: Kuru Exchange: Market-MON/USDC
6 conflicts on slot 0xdfa159d0ee…971576
Audit this contract →
← previous block·next block →recent activity