← previous blocknext block →recent activity
Analyzing
Block #76,024,207
24 transactions · 23 stateful · 2026-05-21 10:10:57 UTC
Parallelism
71/100
Blocked
52%
Avg conflicts / tx
1.25
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #76,024,207 · 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
1w02w13w24w06w37w48w59w610w011w112w215w016w117w221w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcb7b8b2…ebb3
0x065c9d…c394
10 touches
10 conflicts
0x443a3e47…f4a4
0x065c9d…c394
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x8da99e99…690d
0xd32edf…ff58
9 touches
10 conflicts
0x676f9f01…a8ac
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0x0f94ee4c…189a
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 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 0xfcb7b8b239…6bebb3
Audit this contract →
← previous block·next block →recent activity