← previous blocknext block →recent activity
Analyzing
Block #72,370,540
6 transactions · 5 stateful · 2026-05-04 11:50:49 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,370,540 · 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
0x0f2fbb56…9c57
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x70ee67c0…d4a7
0x065c9d…c394
3 touches
1 conflict
0x35dc2ffe…81db
0x065c9d…c394
2 touches
0 conflicts
0xe9c3cc4d…b28d
0x065c9d…c394
2 touches
0 conflicts
0xffe431af…8faa
0x065c9d…c394
2 touches
0 conflicts
0x74e71984…ae90
0x2a68ba…90c5
2 touches
0 conflicts
0x0175b7a6…1db9
0x8d0464…4402
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 0x0f2fbb56b8…749c57
Audit this contract →
← previous block·next block →recent activity