← previous blocknext block →recent activity
Analyzing
Block #72,498,759
24 transactions · 16 stateful · 2026-05-05 02:05:00 UTC
Parallelism
92/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,498,759 · 24 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
1w02w115w018w019w1
- 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
0xf3c24fa1…89dd
0xd32edf…ff58
3 touches
1 conflict
0x13b66f4c…af6b
0x065c9d…c394
3 touches
1 conflict
0xbc154595…08da
0x065c9d…c394
3 touches
1 conflict
0x8ba17998…fbaa
0x065c9d…c394
3 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
2 touches
0 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
1 conflict on slot 0x5c8c6ab6f0…86dc36
Audit this contract →
← previous block·next block →recent activity