Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71d492e70904c2805fb591a9cd1a1c3e49cf47e56445b78297d59c9a891fdd71

Tx prefix hash: ea5637955f065d9712c0f611bec40284d2a1bd892cd2899484743a14a20a59ee
Tx public key: d5071079a4a597012b3cb20aed12379038fe4c21014b709a98c7b6ce646e23e3
Timestamp: 1762994403 Timestamp [UCT]: 2025-11-13 00:40:03 Age [y:d:h:m:s]: 00:038:23:16:28
Block: 1410870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27908 RingCT/type: yes/0
Extra: 01d5071079a4a597012b3cb20aed12379038fe4c21014b709a98c7b6ce646e23e3021100000005e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87f39c9f6c0d213eb5d42e4df3840f7762355c341cdde5e85b5e2392c8da510b 0.600000000000 1899325 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": 1410880, "vin": [ { "gen": { "height": 1410870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87f39c9f6c0d213eb5d42e4df3840f7762355c341cdde5e85b5e2392c8da510b" } } ], "extra": [ 1, 213, 7, 16, 121, 164, 165, 151, 1, 43, 60, 178, 10, 237, 18, 55, 144, 56, 254, 76, 33, 1, 75, 112, 154, 152, 199, 182, 206, 100, 110, 35, 227, 2, 17, 0, 0, 0, 5, 228, 220, 144, 9, 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