← previous blocknext block →recent activity
Analyzing
Block #73,808,206
24 transactions · 22 stateful · 2026-05-11 03:38:14 UTC
Parallelism
67/100
Blocked
77%
Avg conflicts / tx
2.04
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #73,808,206 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w16w27w38w49w510w212w313w414w215w316w417w120w421w522w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0x8240d70c…7c3b
0x34b655…2a6f
10 touches
10 conflicts
0xab41bf9c…66a9
0x34b655…2a6f
8 touches
6 conflicts
0xa91c899f…6ee3
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x408e66bb…3d6b
0x34b655…2a6f
6 touches
3 conflicts
0x22e295f5…1bef
0x065c9d…c394
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity