← previous blocknext block →recent activity
Analyzing
Block #72,971,587
10 transactions · 9 stateful · 2026-05-07 06:35:23 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #72,971,587 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6179b040…809b
0x065c9d…c394
6 touches
3 conflicts
0xea2719bd…916a
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x51f7b5c7…72b1
0x065c9d…c394
4 touches
1 conflict
0x7d6e5575…001e
0x065c9d…c394
4 touches
1 conflict
0xd60000a2…3de1
0x065c9d…c394
4 touches
1 conflict
0xdc21a518…ccd2
0x065c9d…c394
4 touches
1 conflict
0xf25cea8e…3c97
0x065c9d…c394
4 touches
1 conflict
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
3 conflicts on slot 0x6179b040aa…ac809b
Audit this contract →
← previous block·next block →recent activity