← previous blocknext block →recent activity
Analyzing
Block #73,358,530
21 transactions · 19 stateful · 2026-05-09 01:29:56 UTC
Parallelism
71/100
Blocked
42%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #73,358,530 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w08w19w210w111w212w313w314w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0x4d87512b…897c
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x22e295f5…1bef
0x065c9d…c394
6 touches
3 conflicts
0x1ac914d1…e193
0x065c9d…c394
4 touches
1 conflict
0xc2ca855c…dd2a
0x065c9d…c394
4 touches
1 conflict
0xb944d31e…61c2
0x065c9d…c394
4 touches
1 conflict
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