← previous blocknext block →recent activity
Analyzing
Block #73,749,154
36 transactions · 28 stateful · 2026-05-10 21:00:13 UTC
Parallelism
86/100
Blocked
61%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,749,154 · 36 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w06w08w111w212w213w014w117w018w119w020w121w222w325w126w227w328w432w134w235w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x15d039e7…4bb6
0x34b655…2a6f
8 touches
6 conflicts
0xdbe245b8…3c12
0xd32edf…ff58
7 touches
6 conflicts
0xb159af88…a9e7
0x065c9d…c394
6 touches
3 conflicts
0xa904c4d7…675d
0x34b655…2a6f
6 touches
3 conflicts
0xd40bddc1…773c
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
6 touches
3 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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity