← previous blocknext block →recent activity
Analyzing
Block #72,370,504
5 transactions · 5 stateful · 2026-05-04 11:50:35 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,370,504 · 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xe57e835f…2133
0x065c9d…c394
4 touches
1 conflict
0x0c1a8b87…7e1f
0x065c9d…c394
3 touches
1 conflict
0xd94feb0b…f58a
0x065c9d…c394
3 touches
1 conflict
0x65e2e8a1…fe80
0x065c9d…c394
2 touches
0 conflicts
0xb7e8eb0a…e57e
0x065c9d…c394
2 touches
0 conflicts
0xb88da7cd…07af
0x065c9d…c394
2 touches
0 conflicts
0xd01827dc…dcd9
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