← previous blocknext block →recent activity
Analyzing
Block #73,478,519
9 transactions · 9 stateful · 2026-05-09 14:48:24 UTC
Parallelism
44/100
Blocked
44%
Avg conflicts / tx
1.11
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,478,519 · 9 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
2w03w14w25w36w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0xe4b2717a…4cd1
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7f49bbf1…6327
0x065c9d…c394
4 touches
1 conflict
0x9e38f599…3a17
0x065c9d…c394
4 touches
1 conflict
0x7c27250a…7320
0x065c9d…c394
3 touches
1 conflict
0xa7309bc7…9cec
0x065c9d…c394
3 touches
1 conflict
0xb15a08aa…587e
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
6 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity