← previous blocknext block →recent activity
Analyzing
Block #72,295,908
9 transactions · 8 stateful · 2026-05-04 03:33:41 UTC
Parallelism
78/100
Blocked
25%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,295,908 · 9 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
1w02w14w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24968e6d…0132
0x065c9d…c394
4 touches
1 conflict
0xbb1f6c94…3ca5
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x989b8b4f…d19b
0x065c9d…c394
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x94d284f6…ef55
0x065c9d…c394
3 touches
1 conflict
0x35ac0d76…e71d
0x065c9d…c394
3 touches
1 conflict
0x0cfb5d79…7ccc
0x2880ab…7b43
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 0x24968e6db4…f00132
Audit this contract →
← previous block·next block →recent activity