← previous blocknext block →recent activity
Analyzing
Block #72,301,677
7 transactions · 6 stateful · 2026-05-04 04:12:08 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,301,677 · 7 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
1w02w03w14w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf823e97f…2ee6
0x065c9d…c394
4 touches
1 conflict
0x8a35acfb…d1ac
0x8d66a4…3095
4 touches
1 conflict
0x96504a63…52d2
0x8d66a4…3095
4 touches
1 conflict
0xcf3283ba…c9fa
0x065c9d…c394
4 touches
1 conflict
0x7c759cc5…8525
0x065c9d…c394
4 touches
1 conflict
0x075c89ac…f269
0x065c9d…c394
3 touches
1 conflict
0xb15741ef…4631
0x065c9d…c394
3 touches
1 conflict
0x39109867…0a63
0x065c9d…c394
3 touches
1 conflict
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 0xf823e97fa0…262ee6
Audit this contract →
← previous block·next block →recent activity