← previous blocknext block →recent activity
Analyzing
Block #72,214,913
6 transactions · 5 stateful · 2026-05-03 18:29:26 UTC
Parallelism
67/100
Blocked
20%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,214,913 · 6 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7e2af84…4341
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x096b15c9…0e87
0x065c9d…c394
3 touches
1 conflict
0x082c178c…d1af
0x065c9d…c394
3 touches
1 conflict
0x79729867…7c76
0x065c9d…c394
2 touches
0 conflicts
0xa215d0ab…5d95
0x065c9d…c394
2 touches
0 conflicts
0xba809423…9b52
0x065c9d…c394
2 touches
0 conflicts
0xdab207c5…f7e3
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 0xa7e2af84e9…364341
Audit this contract →
← previous block·next block →recent activity