← previous blocknext block →recent activity
Analyzing
Block #73,798,931
9 transactions · 7 stateful · 2026-05-11 02:36:02 UTC
Parallelism
67/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,798,931 · 9 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
3w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7f81fb82…633e
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7aa08522…455c
0x065c9d…c394
3 touches
1 conflict
0xccc4928a…0ff8
0x065c9d…c394
3 touches
1 conflict
0x514a3ad1…ac74
0x065c9d…c394
2 touches
0 conflicts
0x6800eb51…ab70
0x065c9d…c394
2 touches
0 conflicts
0xad37297f…6f9c
0x065c9d…c394
2 touches
0 conflicts
0xb159af88…a9e7
0x065c9d…c394
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
3 conflicts on slot 0x7f81fb82c1…ec633e
Audit this contract →
← previous block·next block →recent activity