← previous blocknext block →recent activity
Analyzing
Block #72,317,013
6 transactions · 6 stateful · 2026-05-04 05:54:17 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,317,013 · 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x37d7b1cc…5a7c
0x065c9d…c394
4 touches
1 conflict
0x729518a9…71f3
0x065c9d…c394
4 touches
1 conflict
0x18c8b56a…3f71
0x065c9d…c394
3 touches
1 conflict
0xeb3bbd43…825a
0x065c9d…c394
3 touches
1 conflict
0x691a92f8…a041
0x065c9d…c394
2 touches
0 conflicts
0x7cbb7b19…1e57
0x065c9d…c394
2 touches
0 conflicts
0xaf218d0c…db4d
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