← previous blocknext block →recent activity
Analyzing
Block #73,807,724
9 transactions · 8 stateful · 2026-05-11 03:35:01 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,807,724 · 9 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
0xe0838f5f…c7ab
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xad55f39e…e096
0x065c9d…c394
3 touches
1 conflict
0x22e295f5…1bef
0x065c9d…c394
2 touches
0 conflicts
0x2ffc27ab…e5d3
0x065c9d…c394
2 touches
0 conflicts
0x494f047e…ee83
0x065c9d…c394
2 touches
0 conflicts
0x85056fb0…ef1b
0x065c9d…c394
2 touches
0 conflicts
0xa13b69d8…b091
0x065c9d…c394
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 0xe0838f5fd1…dec7ab
Audit this contract →
← previous block·next block →recent activity