← previous blocknext block →recent activity
Analyzing
Block #72,500,580
6 transactions · 6 stateful · 2026-05-05 02:17:07 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,500,580 · 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
1w03w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xffe431af…8faa
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x306f08ff…6e91
0x065c9d…c394
2 touches
0 conflicts
0x427a3524…641f
0x065c9d…c394
2 touches
0 conflicts
0x4e939aef…cae0
0x065c9d…c394
2 touches
0 conflicts
0x692953c9…8737
0x065c9d…c394
2 touches
0 conflicts
0x6946d7b5…3c0d
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