← previous blocknext block →recent activity
Analyzing
Block #73,753,442
12 transactions · 10 stateful · 2026-05-10 21:29:07 UTC
Parallelism
75/100
Blocked
40%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,753,442 · 12 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
1w02w13w04w15w06w18w2
- 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
6 touches
3 conflicts
0x6ac48544…a0cc
0x065c9d…c394
4 touches
1 conflict
0x84884534…6437
0x065c9d…c394
4 touches
1 conflict
0x91910343…ed21
0x065c9d…c394
4 touches
1 conflict
0xb159af88…a9e7
0x065c9d…c394
4 touches
1 conflict
0xde1632a4…1d30
0x065c9d…c394
4 touches
1 conflict
0xe1bd8a51…3b24
0x065c9d…c394
4 touches
1 conflict
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