← previous blocknext block →recent activity
Analyzing
Block #76,112,028
16 transactions · 14 stateful · 2026-05-21 19:56:28 UTC
Parallelism
88/100
Blocked
50%
Avg conflicts / tx
0.44
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,112,028 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w06w17w08w19w111w113w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c8c6ab6…dc36
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xffe431af…8faa
0x065c9d…c394
4 touches
1 conflict
0x1c389468…6b0e
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0xfeadc760…8898
0xd32edf…ff58
3 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
1 conflict on slot 0x5c8c6ab6f0…86dc36
Audit this contract →
← previous block·next block →recent activity