← previous blocknext block →recent activity
Analyzing
Block #73,743,842
13 transactions · 10 stateful · 2026-05-10 20:24:20 UTC
Parallelism
77/100
Blocked
20%
Avg conflicts / tx
0.15
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,743,842 · 13 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
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x529acb6a…fcc6
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x05f0c48e…a887
0xd32edf…ff58
3 touches
1 conflict
0x1968940c…4c00
0x065c9d…c394
2 touches
0 conflicts
0x1fe664a9…dfd6
0x065c9d…c394
2 touches
0 conflicts
0x2c9d832f…6bbb
0x065c9d…c394
2 touches
0 conflicts
0xa2922714…86ce
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
1 conflict on slot 0x529acb6ad1…f0fcc6
Audit this contract →
← previous block·next block →recent activity