← previous blocknext block →recent activity
Analyzing
Block #73,642,711
27 transactions · 22 stateful · 2026-05-10 09:02:05 UTC
Parallelism
78/100
Blocked
41%
Avg conflicts / tx
0.74
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #73,642,711 · 27 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w28w09w115w016w118w219w320w321w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x1623fb8a…ebb9
0xd32edf…ff58
5 touches
3 conflicts
0x46cb45de…a566
0x188d58…ea8e
4 touches
1 conflict
0x22e295f5…1bef
0x065c9d…c394
4 touches
1 conflict
0x51ffda3b…18c5
0x065c9d…c394
4 touches
1 conflict
0xd295d35c…7149
0x065c9d…c394
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity