← previous blocknext block →recent activity
Analyzing
Block #72,301,834
8 transactions · 7 stateful · 2026-05-04 04:13:11 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,301,834 · 8 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef9a0989…526f
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x902bfb9d…671b
0x065c9d…c394
3 touches
1 conflict
0x0c8ea6f4…68d4
0x065c9d…c394
2 touches
0 conflicts
0x2b9496ff…50e9
0x065c9d…c394
2 touches
0 conflicts
0x69835b8f…0a4e
0x065c9d…c394
2 touches
0 conflicts
0xa386180f…1dd6
0x065c9d…c394
2 touches
0 conflicts
0xbdb4b7ee…cb4a
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
1 conflict on slot 0xef9a0989d7…75526f
Audit this contract →
← previous block·next block →recent activity