Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa0e22147b6288cf5145734098bbe7cb1a7f418bfca0f0ffd054c5ad17d51aa9

Tx prefix hash: ef1a5f887a2b1eb69c2e08754fb03e3937a91879cddeedeb239da61f1149010d
Tx public key: d962f0ce1983ff2d68b764a857f132f8c7d7b16a5e759e4a616a001822813950
Timestamp: 1742859899 Timestamp [UCT]: 2025-03-24 23:44:59 Age [y:d:h:m:s]: 00:285:00:39:12
Block: 1246582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201523 RingCT/type: yes/0
Extra: 01d962f0ce1983ff2d68b764a857f132f8c7d7b16a5e759e4a616a001822813950021100000004d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24238801f0751627716f7192796812b193bd5c15a4adc2437d04ef338d2ba290 0.600000000000 1733583 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 dinasty-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": 1246592, "vin": [ { "gen": { "height": 1246582 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24238801f0751627716f7192796812b193bd5c15a4adc2437d04ef338d2ba290" } } ], "extra": [ 1, 217, 98, 240, 206, 25, 131, 255, 45, 104, 183, 100, 168, 87, 241, 50, 248, 199, 215, 177, 106, 94, 117, 158, 74, 97, 106, 0, 24, 34, 129, 57, 80, 2, 17, 0, 0, 0, 4, 216, 231, 210, 65, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8