← previous blocknext block →recent activity
Analyzing
Block #73,658,652
6 transactions · 5 stateful · 2026-05-10 10:49:31 UTC
Parallelism
67/100
Blocked
20%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,658,652 · 6 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9e97522…3519
0x2a68ba…90c5
4 touches
1 conflict
0xb28d8fd5…1260
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x568ef37a…8cf2
0x065c9d…c394
2 touches
0 conflicts
0x6e2e75b6…37e9
0x065c9d…c394
2 touches
0 conflicts
0x7916b6a9…fb2a
0x065c9d…c394
2 touches
0 conflicts
0x99390892…e7b5
0x065c9d…c394
2 touches
0 conflicts
0xb159af88…a9e7
0x065c9d…c394
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 0xc9e9752290…9c3519
Audit this contract →
← previous block·next block →recent activity