← previous blocknext block →recent activity
Analyzing
Block #73,479,014
9 transactions · 6 stateful · 2026-05-09 14:51:41 UTC
Parallelism
78/100
Blocked
17%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,479,014 · 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x6f08361d…bda6
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x15bae5fc…9f7e
0x57ea24…2cec
2 touches
0 conflicts
0x192b97ed…b0c9
0x57ea24…2cec
2 touches
0 conflicts
0x2bce8bcd…b3cf
0x57ea24…2cec
2 touches
0 conflicts
0x451f0c72…64f0
0x57ea24…2cec
2 touches
0 conflicts
0x567bb357…50b9
0x57ea24…2cec
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