← previous blocknext block →recent activity
Analyzing
Block #72,309,405
5 transactions · 5 stateful · 2026-05-04 05:03:38 UTC
Parallelism
60/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,309,405 · 5 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2ddcfa6d…a5dc
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb5d56cb5…10a0
0x065c9d…c394
3 touches
1 conflict
0x62b62804…1cd9
0x065c9d…c394
3 touches
1 conflict
0xb0bfe9e1…2b0c
0x065c9d…c394
2 touches
0 conflicts
0xc452ad02…982c
0x065c9d…c394
2 touches
0 conflicts
0xccaaa85f…86db
0x065c9d…c394
2 touches
0 conflicts
0xcf3283ba…c9fa
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 0x2ddcfa6d91…68a5dc
Audit this contract →
← previous block·next block →recent activity