← previous blocknext block →recent activity
Analyzing
Block #73,038,210
26 transactions · 16 stateful · 2026-05-07 13:58:50 UTC
Parallelism
88/100
Blocked
38%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,038,210 · 26 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
1w02w13w04w16w217w018w224w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd7e37a9…9eb5
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x0b390c61…dc07
0x065c9d…c394
6 touches
3 conflicts
0xebd595ad…c5da
0xd32edf…ff58
5 touches
3 conflicts
0x65212fb0…dbef
0x065c9d…c394
4 touches
1 conflict
0x9ef53a58…190c
0x065c9d…c394
4 touches
1 conflict
0x3539de7c…9d32
0x065c9d…c394
4 touches
1 conflict
0xe662fc0f…25da
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
3 conflicts on slot 0xbd7e37a9b5…859eb5
Audit this contract →
← previous block·next block →recent activity