← previous blocknext block →recent activity
Analyzing
Block #73,348,132
13 transactions · 9 stateful · 2026-05-09 00:20:49 UTC
Parallelism
85/100
Blocked
11%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,348,132 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x22e295f5…1bef
0x065c9d…c394
4 touches
1 conflict
0x3da01c6f…2800
0x065c9d…c394
3 touches
1 conflict
0x4541c79f…42dc
0x065c9d…c394
2 touches
0 conflicts
0xbdff944d…447e
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…0002
0xab3526…fa38
2 touches
0 conflicts
0x0175b7a6…1dba
0xaba216…a862
2 touches
0 conflicts
0x0175b7a6…1dbc
0xaba216…a862
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity