← previous blocknext block →recent activity
Analyzing
Block #72,570,974
39 transactions · 29 stateful · 2026-05-05 10:05:48 UTC
Parallelism
77/100
Blocked
66%
Avg conflicts / tx
1.15
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #72,570,974 · 39 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w19w010w112w113w114w015w116w220w021w122w023w124w225w328w529w631w132w734w735w837w238w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0x93ed6b22…f6da
0xd32edf…ff58
11 touches
15 conflicts
0x24968e6d…0132
0x065c9d…c394
10 touches
10 conflicts
0xbb1747e2…f78b
0x34b655…2a6f
8 touches
6 conflicts
0xbbee74c2…567a
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0002
0x7e9d3a…9fda
6 touches
3 conflicts
0xbf04f37d…85f2
0x2a68ba…90c5
4 touches
1 conflict
0xcce2fd99…a8eb
0x3bd359…433a
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
15 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity