← previous blocknext block →recent activity
Analyzing
Block #72,285,355
11 transactions · 9 stateful · 2026-05-04 02:22:49 UTC
Parallelism
73/100
Blocked
22%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #72,285,355 · 11 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
1w02w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x24968e6d…0132
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2c6c48a9…ba4a
0x065c9d…c394
2 touches
0 conflicts
0x4a324d60…e27a
0x065c9d…c394
2 touches
0 conflicts
0x639f478c…ed77
0x065c9d…c394
2 touches
0 conflicts
0x7d0c513f…97cd
0x065c9d…c394
2 touches
0 conflicts
0x74e71984…ae90
0x2a68ba…90c5
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity