← previous blocknext block →recent activity
Analyzing
Block #73,697,815
41 transactions · 35 stateful · 2026-05-10 15:13:42 UTC
Parallelism
73/100
Blocked
66%
Avg conflicts / tx
1.78
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #73,697,815 · 41 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w09w310w414w126w327w428w529w631w532w633w734w835w936w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
16 touches
28 conflicts
0x72ce4690…4ee2
0xd32edf…ff58
13 touches
21 conflicts
0x529acb6a…fcc6
0x065c9d…c394
10 touches
10 conflicts
0xf2438038…5fa7
0x34b655…2a6f
10 touches
10 conflicts
0x0ac31945…2c72
0x065c9d…c394
10 touches
10 conflicts
0x00000000…002c
0x1b6862…e19c
8 touches
6 conflicts
0xe937b6bc…8a58
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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
28 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity