← previous blocknext block →recent activity
Analyzing
Block #72,370,511
7 transactions · 6 stateful · 2026-05-04 11:50:37 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,370,511 · 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbf83d802…6004
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xacf23f02…3aa2
0x065c9d…c394
3 touches
1 conflict
0x096818a6…0e9f
0x065c9d…c394
2 touches
0 conflicts
0x0d65528b…85da
0x065c9d…c394
2 touches
0 conflicts
0x23506d63…0127
0x065c9d…c394
2 touches
0 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
2 touches
0 conflicts
0x65e2e8a1…fe80
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 0xbf83d802d2…6d6004
Audit this contract →
← previous block·next block →recent activity