← previous blocknext block →recent activity
Analyzing
Block #72,301,606
6 transactions · 6 stateful · 2026-05-04 04:11:40 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,301,606 · 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x45ebb33b…5fcc
0x065c9d…c394
2 touches
0 conflicts
0x60a02806…7d8d
0x065c9d…c394
2 touches
0 conflicts
0x7160ce22…f3aa
0x065c9d…c394
2 touches
0 conflicts
0x74747f6f…e787
0x065c9d…c394
2 touches
0 conflicts
0x9112234f…d9d2
0x065c9d…c394
2 touches
0 conflicts
0xa708f77b…ff5e
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity