← previous blocknext block →recent activity
Analyzing
Block #73,753,668
14 transactions · 13 stateful · 2026-05-10 21:30:38 UTC
Parallelism
57/100
Blocked
46%
Avg conflicts / tx
1.43
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #73,753,668 · 14 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
1w04w05w16w27w38w49w512w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xc0c926e4…ad29
0x065c9d…c394
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x4946e1bd…8ec6
0x065c9d…c394
4 touches
1 conflict
0x2766d6d3…a260
0x065c9d…c394
3 touches
1 conflict
0xee670f7b…5079
0x065c9d…c394
3 touches
1 conflict
0xc506cbf2…dc62
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
15 conflicts on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity