← previous blocknext block →recent activity
Analyzing
Block #76,090,793
26 transactions · 18 stateful · 2026-05-21 17:35:03 UTC
Parallelism
88/100
Blocked
28%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,090,793 · 26 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
1w02w07w19w211w012w113w223w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x41755291…977f
0x065c9d…c394
6 touches
3 conflicts
0x6ac11407…0bcc
0x3bd359…433a
6 touches
3 conflicts
0xa472d565…9fe4
0x3bd359…433a
6 touches
3 conflicts
0x44ad89ba…cf83
0xd10cf1…7777
6 touches
3 conflicts
0x5180f24b…0b96
0xd10cf1…7777
6 touches
3 conflicts
0x00000000…0000
0xd57e82…8ed4
6 touches
3 conflicts
0x00000000…0001
0xd57e82…8ed4
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity