← previous blocknext block →recent activity
Analyzing
Block #72,284,896
10 transactions · 9 stateful · 2026-05-04 02:19:44 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,284,896 · 10 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
2w04w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7894e716…1a66
0x065c9d…c394
4 touches
1 conflict
0xea49073f…2c21
0xd32edf…ff58
3 touches
1 conflict
0x139ed51f…bd2b
0x065c9d…c394
3 touches
1 conflict
0x95459c8d…4ac9
0x065c9d…c394
3 touches
1 conflict
0xdb7431af…b258
0x065c9d…c394
3 touches
1 conflict
0xe5b4c4cb…680a
0x065c9d…c394
3 touches
1 conflict
0x24968e6d…0132
0x065c9d…c394
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
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 0x7894e716b9…b71a66
Audit this contract →
← previous block·next block →recent activity