Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 922f94e6e0d2533a0b2ab26171f75113d5400d1b594d90e944c7ef78e7600a9e

Tx prefix hash: 00c8e6d719d05db5e946071e7da424dedb509b48ee73f058ff1434d5b65e3fc0
Tx public key: 2fd0cf7f99b5ef8d05958ce3db483d06713b2fb0a42c7c72a308e2c0a7a0900d
Timestamp: 1735060336 Timestamp [UCT]: 2024-12-24 17:12:16 Age [y:d:h:m:s]: 00:034:12:41:26
Block: 1182310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24433 RingCT/type: yes/0
Extra: 012fd0cf7f99b5ef8d05958ce3db483d06713b2fb0a42c7c72a308e2c0a7a0900d021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 795579161bee1d77153ba2dca94474ef3353effd653e83445badac7c8a3103cc 0.600000000000 1668743 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": 1182320, "vin": [ { "gen": { "height": 1182310 } } ], "vout": [ { "amount": 600000000, "target": { "key": "795579161bee1d77153ba2dca94474ef3353effd653e83445badac7c8a3103cc" } } ], "extra": [ 1, 47, 208, 207, 127, 153, 181, 239, 141, 5, 149, 140, 227, 219, 72, 61, 6, 113, 59, 47, 176, 164, 44, 124, 114, 163, 8, 226, 192, 167, 160, 144, 13, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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