← previous blocknext block →recent activity
Analyzing
Block #72,971,053
32 transactions · 22 stateful · 2026-05-07 06:31:50 UTC
Parallelism
69/100
Blocked
55%
Avg conflicts / tx
1.03
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #72,971,053 · 32 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w310w317w419w520w621w422w523w724w825w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0x046a928e…0012
0x2a68ba…90c5
10 touches
10 conflicts
0x7f189cf6…afab
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x2271cbab…fb4d
0xd32edf…ff58
7 touches
6 conflicts
0x9c47cbd4…7370
0x065c9d…c394
4 touches
2 conflicts
0x70b2f813…783c
0x2a68ba…90c5
4 touches
1 conflict
0xf72da517…50ed
0x065c9d…c394
3 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
15 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity