← previous blocknext block →recent activity
Analyzing
Block #73,751,021
18 transactions · 14 stateful · 2026-05-10 21:12:49 UTC
Parallelism
83/100
Blocked
43%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,751,021 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w18w29w110w211w012w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x37f7aa99…43c0
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x337b7116…5304
0xd32edf…ff58
5 touches
3 conflicts
0xd46cd782…e7f2
0x7131ec…7777
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…0000
0xc82b5c…bb3a
4 touches
1 conflict
0x00000000…0001
0xc82b5c…bb3a
4 touches
1 conflict
0x00000000…001d
0x1b6862…e19c
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
3 conflicts on slot 0x37f7aa9967…5043c0
Audit this contract →
← previous block·next block →recent activity