← previous blocknext block →recent activity
Analyzing
Block #76,042,623
23 transactions · 22 stateful · 2026-05-21 12:13:33 UTC
Parallelism
74/100
Blocked
64%
Avg conflicts / tx
1.3
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #76,042,623 · 23 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
1w02w13w24w05w16w37w48w510w011w112w213w014w115w219w320w221w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x3b86caa0…a2a9
0x34b655…2a6f
8 touches
6 conflicts
0x676f9f01…a8ac
0x34b655…2a6f
8 touches
6 conflicts
0x4e72c9bd…9ce4
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002b
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity