← previous blocknext block →recent activity
Analyzing
Block #73,979,243
14 transactions · 10 stateful · 2026-05-11 22:37:39 UTC
Parallelism
79/100
Blocked
30%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,979,243 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w212w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x0eac6378…36f4
0x34b655…2a6f
4 touches
1 conflict
0x1d1799a9…c621
0x34b655…2a6f
4 touches
1 conflict
0x070a562a…8147
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xcc21c659…adea
0x065c9d…c394
4 touches
1 conflict
0xa15427f6…d932
0x34b655…2a6f
4 touches
1 conflict
0xba5743c7…21c1
0x1b6862…e19c
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
3 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity