← previous blocknext block →recent activity
Analyzing
Block #73,751,221
19 transactions · 17 stateful · 2026-05-10 21:14:10 UTC
Parallelism
79/100
Blocked
29%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,751,221 · 19 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
3w04w05w06w17w28w09w112w013w114w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xed57bddf…1abf
0xc8689a…ee79
6 touches
3 conflicts
0x8c265bdf…3604
0xd32edf…ff58
5 touches
3 conflicts
0xc5564f8e…f4bf
0x6c4bfa…a540
5 touches
3 conflicts
0x01ae3085…6a0b
0x065c9d…c394
4 touches
3 conflicts
0xcb45d9d6…cb85
0x1b6862…e19c
4 touches
1 conflict
0xc9e97522…3519
0x2a68ba…90c5
4 touches
1 conflict
0x7c403af1…31b1
0x3bd359…433a
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity