← previous blocknext block →recent activity
Analyzing
Block #73,705,137
18 transactions · 18 stateful · 2026-05-10 16:03:06 UTC
Parallelism
44/100
Blocked
67%
Avg conflicts / tx
2.89
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #73,705,137 · 18 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w07w29w310w311w412w513w614w715w816w917w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
18 touches
36 conflicts
0x529acb6a…fcc6
0x065c9d…c394
14 touches
21 conflicts
0x0ac31945…2c72
0x065c9d…c394
12 touches
15 conflicts
0x046a928e…0012
0x2a68ba…90c5
10 touches
10 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xc9e97522…3519
0x2a68ba…90c5
6 touches
3 conflicts
0x6848c89c…43d9
0x065c9d…c394
5 touches
3 conflicts
0x87d79ddf…9e75
0x065c9d…c394
5 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
36 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity