← previous blocknext block →recent activity
Analyzing
Block #73,377,470
16 transactions · 16 stateful · 2026-05-09 03:35:57 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
1.63
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #73,377,470 · 16 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w07w18w29w310w411w512w613w7
- 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
10 touches
10 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
10 touches
10 conflicts
0x22e295f5…1bef
0x065c9d…c394
6 touches
3 conflicts
0x4d87512b…897c
0x065c9d…c394
4 touches
1 conflict
0x1e12c4d4…9064
0x065c9d…c394
4 touches
1 conflict
0x59ca7a19…4fcb
0x065c9d…c394
4 touches
1 conflict
0x68faa0b9…14af
0x368ee5…7ca4
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
10 conflicts on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity