← previous blocknext block →recent activity
Analyzing
Block #73,417,721
25 transactions · 22 stateful · 2026-05-09 08:03:56 UTC
Parallelism
60/100
Blocked
50%
Avg conflicts / tx
1.68
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #73,417,721 · 25 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
1w02w13w24w05w37w113w314w415w519w620w721w822w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
16 touches
28 conflicts
0x046a928e…0012
0x2a68ba…90c5
12 touches
15 conflicts
0x6f08361d…bda6
0x065c9d…c394
8 touches
6 conflicts
0x22e295f5…1bef
0x065c9d…c394
8 touches
6 conflicts
0xf537eaa0…73c8
0x065c9d…c394
8 touches
6 conflicts
0x5a08a99d…f047
0xd32edf…ff58
5 touches
3 conflicts
0xed482014…03f8
0x065c9d…c394
5 touches
3 conflicts
0x00000000…0015
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
28 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity