← previous blocknext block →recent activity
Analyzing
Block #76,603,341
23 transactions · 19 stateful · 2026-05-24 02:28:02 UTC
Parallelism
83/100
Blocked
53%
Avg conflicts / tx
0.96
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,603,341 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w17w08w19w211w012w113w014w115w216w120w321w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xcc4f1f14…aa5f
0x065c9d…c394
8 touches
6 conflicts
0xdfa159d0…1576
0x065c9d…c394
8 touches
6 conflicts
0x9cbd07e8…b7bd
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
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity