← previous blocknext block →recent activity
Analyzing
Block #73,035,388
22 transactions · 17 stateful · 2026-05-07 13:40:03 UTC
Parallelism
73/100
Blocked
53%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #73,035,388 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w18w29w010w111w214w315w416w520w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b390c61…dc07
0x065c9d…c394
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xdaca243a…f9de
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1ac
0x8d66a4…3095
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xbd7e37a9…9eb5
0x065c9d…c394
6 touches
3 conflicts
0xe7535190…5a0f
0x6ca43f…c331
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
10 conflicts on slot 0x0b390c6160…02dc07
Audit this contract →
← previous block·next block →recent activity