Dinastycoin Explorer Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: f3ac5618ed0a4ae58f1f76d7001c19304bb2385d72db5fa76ba330988f32ddfa

Tx prefix hash: a2d55035e391c760c9f8105234075ac36c5fb77aebcb9b0760552f9679b7acac
Tx public key: 759884e8327edde30333d5b494d7bfafd1955f78f897cc143a7a2f71e4a11c40
Timestamp: 1709413343 Timestamp [UTC]: 2024-03-02 21:02:23 Age [y:d:h:m:s]: 02:262:00:09:21
Block: 969791 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 712370 RingCT/type: yes/0
Extra: 01759884e8327edde30333d5b494d7bfafd1955f78f897cc143a7a2f71e4a11c400211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c2232ede80fed53bfbea52f49a5c27d42a7a4ff57ce58b7ba575911fbbd0871d 0.000600000000 1429636 of 15 -

Check which outputs belong to given dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinastycoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 969801, "vin": [ { "gen": { "height": 969791 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2232ede80fed53bfbea52f49a5c27d42a7a4ff57ce58b7ba575911fbbd0871d" } } ], "extra": [ 1, 117, 152, 132, 232, 50, 126, 221, 227, 3, 51, 213, 180, 148, 215, 191, 175, 209, 149, 95, 120, 248, 151, 204, 20, 58, 122, 47, 113, 228, 161, 28, 64, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: