← previous blocknext block →recent activity
Analyzing
Block #72,285,363
9 transactions · 8 stateful · 2026-05-04 02:22:53 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #72,285,363 · 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
2w03w15w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23e11a62…5906
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xfbacfc98…1934
0x065c9d…c394
5 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x99751520…f7df
0x065c9d…c394
3 touches
1 conflict
0x4a324d60…e27a
0x065c9d…c394
2 touches
0 conflicts
0x639f478c…ed77
0x065c9d…c394
2 touches
0 conflicts
0x7d0c513f…97cd
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 0x23e11a6216…a55906
Audit this contract →
← previous block·next block →recent activity