← previous blocknext block →recent activity
Analyzing
Block #73,360,684
11 transactions · 11 stateful · 2026-05-09 01:44:14 UTC
Parallelism
64/100
Blocked
27%
Avg conflicts / tx
0.73
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,360,684 · 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
1w04w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x0be89b16…a75e
0x065c9d…c394
2 touches
0 conflicts
0x47e16a45…f5d4
0x065c9d…c394
2 touches
0 conflicts
0x85174568…10ac
0x065c9d…c394
2 touches
0 conflicts
0x86e62424…9526
0x065c9d…c394
2 touches
0 conflicts
0xc3cdc1a0…f298
0x065c9d…c394
2 touches
0 conflicts
0xe70c9d85…74df
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: MarginAccount
6 conflicts on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity