← previous blocknext block →recent activity
Analyzing
Block #72,232,955
7 transactions · 6 stateful · 2026-05-03 20:30:39 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,232,955 · 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2cba831…afba
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x90c08a76…2af8
0x065c9d…c394
4 touches
1 conflict
0xb0108b33…9df3
0x065c9d…c394
3 touches
1 conflict
0x99d4900e…973a
0x065c9d…c394
3 touches
1 conflict
0x0e9dbd3a…ac20
0x065c9d…c394
3 touches
1 conflict
0x081a3c8a…e1ad
0x065c9d…c394
3 touches
1 conflict
0x95e92f18…3dfb
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 0xe2cba83164…31afba
Audit this contract →
← previous block·next block →recent activity