← previous blocknext block →recent activity
Analyzing
Block #73,642,459
30 transactions · 24 stateful · 2026-05-10 09:00:22 UTC
Parallelism
77/100
Blocked
67%
Avg conflicts / tx
1.1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #73,642,459 · 30 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w05w16w27w38w09w110w211w314w115w218w319w420w521w622w126w227w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x22e295f5…1bef
0x065c9d…c394
8 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…0002
0xab3526…fa38
8 touches
6 conflicts
0xc6417de0…2191
0xc8689a…ee79
6 touches
3 conflicts
0x13023f15…3eb2
0x34b655…2a6f
6 touches
3 conflicts
0x57de3828…3fbb
0x34b655…2a6f
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