← previous blocknext block →recent activity
Analyzing
Block #76,256,246
27 transactions · 21 stateful · 2026-05-22 11:57:00 UTC
Parallelism
81/100
Blocked
48%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,256,246 · 27 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
9w010w111w212w315w016w118w019w120w223w424w225w326w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41755291…977f
0x065c9d…c394
10 touches
10 conflicts
0x801a6e57…d85c
0x34b655…2a6f
10 touches
10 conflicts
0x47b807a2…3307
0x065c9d…c394
8 touches
6 conflicts
0xfbf19dcd…3af0
0xd32edf…ff58
7 touches
6 conflicts
0x99a21305…dffc
0x2a68ba…90c5
6 touches
3 conflicts
0xfe2bac2b…2cec
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
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
10 conflicts on slot 0x4175529119…79977f
Audit this contract →
← previous block·next block →recent activity