← previous blocknext block →recent activity
Analyzing
Block #72,318,063
10 transactions · 9 stateful · 2026-05-04 06:01:16 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,318,063 · 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
2w06w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbbee74c2…567a
0x065c9d…c394
4 touches
1 conflict
0xe7e6c995…e829
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x74b22cab…518a
0x065c9d…c394
3 touches
1 conflict
0xcaa4cc8b…b279
0x065c9d…c394
2 touches
0 conflicts
0xcaa4cc8b…b27a
0x065c9d…c394
2 touches
0 conflicts
0xcb2d71bb…ff69
0x065c9d…c394
2 touches
0 conflicts
0x74e71984…ae90
0x2a68ba…90c5
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 0xbbee74c2e7…6e567a
Audit this contract →
← previous block·next block →recent activity