← previous blocknext block →recent activity
Analyzing
Block #73,202,368
10 transactions · 9 stateful · 2026-05-08 08:11:06 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,202,368 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7f189cf6…afab
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x92339d95…0800
0x0000a8…8888
2 touches
0 conflicts
0x3336c366…a5ef
0x065c9d…c394
2 touches
0 conflicts
0xd4bb575f…1737
0x065c9d…c394
2 touches
0 conflicts
0xeea47431…1ce9
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 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
6 conflicts on slot 0x7f189cf621…beafab
Audit this contract →
← previous block·next block →recent activity