Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 62db457b179736ee5db2666cf262f358bcf18b8a5f2ff93d81e43bd07162c61a

Tx prefix hash: 73921e860fab7c05d567b97becf5102cb25ddd9b112bd7e89bc220d7ad11873d
Tx public key: 06461581207ebf56b47b4ed0e4a4ba8afb5720a299101a1f5c05c546683d3a32
Timestamp: 1716338703 Timestamp [UCT]: 2024-05-22 00:45:03 Age [y:d:h:m:s]: 01:016:07:43:08
Block: 1027206 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272585 RingCT/type: yes/0
Extra: 0106461581207ebf56b47b4ed0e4a4ba8afb5720a299101a1f5c05c546683d3a320211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eac6a1962bc2a3a54e434e8298740a8b5895add68d408a3b3769cdc1b34efe15 0.600000000000 1494707 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": 1027216, "vin": [ { "gen": { "height": 1027206 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eac6a1962bc2a3a54e434e8298740a8b5895add68d408a3b3769cdc1b34efe15" } } ], "extra": [ 1, 6, 70, 21, 129, 32, 126, 191, 86, 180, 123, 78, 208, 228, 164, 186, 138, 251, 87, 32, 162, 153, 16, 26, 31, 92, 5, 197, 70, 104, 61, 58, 50, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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