← previous blocknext block →recent activity
Analyzing
Block #73,697,931
15 transactions · 9 stateful · 2026-05-10 15:14:30 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,697,931 · 15 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
1w07w010w111w212w3
- 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
8 touches
6 conflicts
0x529acb6a…fcc6
0x065c9d…c394
6 touches
3 conflicts
0x5f3895b2…c978
0x065c9d…c394
3 touches
1 conflict
0x925ae80a…cbe0
0x065c9d…c394
3 touches
1 conflict
0xa13550ef…c573
0x065c9d…c394
2 touches
0 conflicts
0x4dd1db39…a994
0x188d58…ea8e
2 touches
0 conflicts
0x4dd1db39…a996
0x188d58…ea8e
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