← previous blocknext block →recent activity
Analyzing
Block #73,416,479
11 transactions · 9 stateful · 2026-05-09 07:55:38 UTC
Parallelism
64/100
Blocked
33%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,416,479 · 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
5w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x14a4ad11…ff04
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x8a70cb21…1dc1
0x065c9d…c394
3 touches
1 conflict
0xb8eab5cd…5ca4
0x065c9d…c394
3 touches
1 conflict
0x8147d2f3…c172
0x065c9d…c394
2 touches
0 conflicts
0x9f512c52…b679
0x065c9d…c394
2 touches
0 conflicts
0xa33757c0…29e5
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
3 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity