Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30ed45e06f0166ebd28a2d092a81e05580281eac6455e9dc6dbdbe5cd33404f2

Tx prefix hash: 21fb1d2158063e64223bc6fd1f1d03e1013a5533eac820b6bc08af2398aab3f0
Tx public key: 143f8a098cef7eddf4551723830cb0016812f4ede156ef6c888285e8a513f512
Timestamp: 1581541383 Timestamp [UCT]: 2020-02-12 21:03:03 Age [y:d:h:m:s]: 04:294:01:41:17
Block: 63730 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1102273 RingCT/type: yes/0
Extra: 01143f8a098cef7eddf4551723830cb0016812f4ede156ef6c888285e8a513f5120211000000054ac5aa02000000000000000000

1 output(s) for total of 377.454081265000 dcy

stealth address amount amount idx
00: 7e262e34447b9011a85341e0e064c8306e06be46e21ec26bfb4349622e05c815 377.454081265000 117457 of 0

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": 63740, "vin": [ { "gen": { "height": 63730 } } ], "vout": [ { "amount": 377454081265, "target": { "key": "7e262e34447b9011a85341e0e064c8306e06be46e21ec26bfb4349622e05c815" } } ], "extra": [ 1, 20, 63, 138, 9, 140, 239, 126, 221, 244, 85, 23, 35, 131, 12, 176, 1, 104, 18, 244, 237, 225, 86, 239, 108, 136, 130, 133, 232, 165, 19, 245, 18, 2, 17, 0, 0, 0, 5, 74, 197, 170, 2, 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