← previous blocknext block →recent activity
Analyzing
Block #73,437,502
13 transactions · 10 stateful · 2026-05-09 10:15:27 UTC
Parallelism
85/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,437,502 · 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d207d97…0715
0x065c9d…c394
4 touches
1 conflict
0x72d12d93…92cf
0x065c9d…c394
4 touches
1 conflict
0x22e295f5…1bef
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x87ee97a4…89a6
0x065c9d…c394
3 touches
1 conflict
0x195ab8fe…38fc
0x065c9d…c394
3 touches
1 conflict
0xed482014…03f8
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 0x5d207d970c…960715
Audit this contract →
← previous block·next block →recent activity