← previous blocknext block →recent activity
Analyzing
Block #76,090,626
22 transactions · 15 stateful · 2026-05-21 17:33:56 UTC
Parallelism
86/100
Blocked
47%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,090,626 · 22 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w27w08w19w210w114w220w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0xb1934d18…533f
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x41755291…977f
0x065c9d…c394
4 touches
1 conflict
0x50e10826…843b
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1a8
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1a9
0x8d66a4…3095
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity