← previous blocknext block →recent activity
Analyzing
Block #73,035,926
16 transactions · 11 stateful · 2026-05-07 13:43:38 UTC
Parallelism
81/100
Blocked
27%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,035,926 · 16 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
1w02w13w24w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70b2f813…783c
0x2a68ba…90c5
4 touches
1 conflict
0xba5743c7…21c6
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0002
0xd574ca…7ab1
4 touches
1 conflict
0x4b155234…0aa2
0xd32edf…ff58
3 touches
1 conflict
0xf6a82949…5b9f
0x065c9d…c394
3 touches
1 conflict
0x8876d94c…8435
0x2a68ba…90c5
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
1 conflict on slot 0x70b2f81398…04783c
Audit this contract →
← previous block·next block →recent activity