← previous blocknext block →recent activity
Analyzing
Block #73,014,772
41 transactions · 32 stateful · 2026-05-07 11:22:51 UTC
Parallelism
81/100
Blocked
66%
Avg conflicts / tx
1.61
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #73,014,772 · 41 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
1w02w18w211w013w314w116w117w218w324w225w328w429w530w633w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
14 touches
21 conflicts
0x0b390c61…dc07
0x065c9d…c394
12 touches
15 conflicts
0x797d87f1…2d7b
0xd32edf…ff58
11 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x30e87049…4a0e
0x065c9d…c394
8 touches
8 conflicts
0x70b2f813…783c
0x2a68ba…90c5
8 touches
6 conflicts
0x47c1a8e8…f74a
0x34b655…2a6f
8 touches
6 conflicts
0xb5e1ef4c…cd43
0x065c9d…c394
8 touches
6 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
21 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity