← previous blocknext block →recent activity
Analyzing
Block #72,309,413
25 transactions · 20 stateful · 2026-05-04 05:03:41 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
0.72
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #72,309,413 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w18w09w114w015w216w317w419w520w621w723w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x7f312931…d6af
0xd32edf…ff58
7 touches
6 conflicts
0xc3c8642a…7da5
0x2a68ba…90c5
6 touches
3 conflicts
0x14c49dbb…2cb1
0x065c9d…c394
5 touches
3 conflicts
0x7b7bcac3…8fbf
0x34b655…2a6f
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xcce2fd99…a8eb
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x659bd0…a9da
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity