← previous blocknext block →recent activity
Analyzing
Block #73,672,563
11 transactions · 9 stateful · 2026-05-10 12:23:20 UTC
Parallelism
64/100
Blocked
33%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,672,563 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x529acb6a…fcc6
0x065c9d…c394
8 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x3b0511b9…98f4
0x065c9d…c394
2 touches
0 conflicts
0x88d6f254…206b
0x065c9d…c394
2 touches
0 conflicts
0x957d776e…15d2
0x065c9d…c394
2 touches
0 conflicts
0xa299b34d…b4fd
0x065c9d…c394
2 touches
0 conflicts
0xa56b90b4…8343
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
6 conflicts on slot 0x529acb6ad1…f0fcc6
Audit this contract →
← previous block·next block →recent activity