Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 471d2a628a154d3c3942cb39f64bdf4056470b7695ff5816191b144cb1569f4d

Tx prefix hash: a93096e3d910c01c63dbefba2b8d0e5431cf990b37dc71539202b71d8261e4ca
Tx public key: 715c82956c66fb2870939f523823e4fd048199b10a084d326c3c5ebf36af646a
Timestamp: 1748144333 Timestamp [UCT]: 2025-05-25 03:38:53 Age [y:d:h:m:s]: 00:172:15:47:51
Block: 1290351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121077 RingCT/type: yes/0
Extra: 01715c82956c66fb2870939f523823e4fd048199b10a084d326c3c5ebf36af646a021100000004a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d580c04f0503c225289a53081de95ef0b9a558f648207b968c12aac1fa0c316 0.600000000000 1777820 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": 1290361, "vin": [ { "gen": { "height": 1290351 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d580c04f0503c225289a53081de95ef0b9a558f648207b968c12aac1fa0c316" } } ], "extra": [ 1, 113, 92, 130, 149, 108, 102, 251, 40, 112, 147, 159, 82, 56, 35, 228, 253, 4, 129, 153, 177, 10, 8, 77, 50, 108, 60, 94, 191, 54, 175, 100, 106, 2, 17, 0, 0, 0, 4, 161, 29, 186, 152, 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