← previous blocknext block →recent activity
Analyzing
Block #73,670,421
14 transactions · 12 stateful · 2026-05-10 12:08:51 UTC
Parallelism
57/100
Blocked
58%
Avg conflicts / tx
1.36
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #73,670,421 · 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
1w02w06w17w18w29w310w411w513w1
- 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
8 touches
6 conflicts
0x529acb6a…fcc6
0x065c9d…c394
6 touches
3 conflicts
0x0ac31945…2c72
0x065c9d…c394
4 touches
1 conflict
0x12235f63…a567
0x065c9d…c394
4 touches
1 conflict
0xf2438038…5fa7
0x34b655…2a6f
4 touches
1 conflict
0x84630c7f…21f4
0x065c9d…c394
4 touches
1 conflict
0x49fd26c2…8d84
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
10 conflicts on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity