← previous blocknext block →recent activity
Analyzing
Block #73,638,182
14 transactions · 12 stateful · 2026-05-10 08:31:35 UTC
Parallelism
50/100
Blocked
58%
Avg conflicts / tx
0.86
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #73,638,182 · 14 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w08w39w410w511w613w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x4d87512b…897c
0x065c9d…c394
6 touches
3 conflicts
0x22e295f5…1bef
0x065c9d…c394
4 touches
1 conflict
0xb81d3ee7…3947
0x34b655…2a6f
4 touches
1 conflict
0x48c579b1…6f98
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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
6 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity