← previous blocknext block →recent activity
Analyzing
Block #76,603,473
13 transactions · 10 stateful · 2026-05-24 02:28:55 UTC
Parallelism
69/100
Blocked
50%
Avg conflicts / tx
0.77
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,603,473 · 13 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
1w02w14w25w26w37w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc4f1f14…aa5f
0x065c9d…c394
8 touches
6 conflicts
0xdfa159d0…1576
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c5
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
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 0xcc4f1f1446…7caa5f
Audit this contract →
← previous block·next block →recent activity