← previous blocknext block →recent activity
Analyzing
Block #73,438,460
11 transactions · 9 stateful · 2026-05-09 10:21:48 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,438,460 · 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
6w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x213ea25b…f763
0x065c9d…c394
4 touches
1 conflict
0x6f08361d…bda6
0x065c9d…c394
2 touches
0 conflicts
0xe4d58309…5b16
0x065c9d…c394
2 touches
0 conflicts
0x4c770fe0…b972
0x3bd359…433a
2 touches
0 conflicts
0xa472d565…9fe4
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0000
0x714a26…182d
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 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity