← previous blocknext block →recent activity
Analyzing
Block #76,447,927
22 transactions · 20 stateful · 2026-05-23 09:13:12 UTC
Parallelism
64/100
Blocked
70%
Avg conflicts / tx
1.36
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #76,447,927 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w26w37w48w59w610w611w712w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc8faac2…c766
0x065c9d…c394
10 touches
10 conflicts
0x18cf3003…51d1
0x065c9d…c394
8 touches
6 conflicts
0x8bc3e255…0a0b
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x99a21305…dffc
0x2a68ba…90c5
6 touches
3 conflicts
0x388f889f…a655
0x34b655…2a6f
6 touches
3 conflicts
0x65903ef9…2567
0x34b655…2a6f
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 0xcc8faac238…88c766
Audit this contract →
← previous block·next block →recent activity