← previous blocknext block →recent activity
Analyzing
Block #73,496,481
14 transactions · 13 stateful · 2026-05-09 16:47:56 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
1.07
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,496,481 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w17w08w19w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xa8857b10…f40e
0x065c9d…c394
4 touches
1 conflict
0x22e295f5…1bef
0x065c9d…c394
4 touches
1 conflict
0x37047e6f…9757
0x065c9d…c394
4 touches
1 conflict
0x7c88afb9…b9e2
0x065c9d…c394
3 touches
1 conflict
0xd4fe83ec…32be
0x065c9d…c394
3 touches
1 conflict
0xebc790e2…5ef9
0x065c9d…c394
3 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
10 conflicts on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity