Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5ae39df54d228bc84e9adfba790ecf1da26f6e4be8435759f6c2f0212ccfcd3

Tx prefix hash: 65aca0a4b1b04830dad92157ed1f8896274ebf00673f035bba41ed08fc39795f
Tx public key: 99a9186f4fea02c8db8243177733cd129f97343c29e8c4bb41f48fef35f77a3f
Timestamp: 1592761141 Timestamp [UCT]: 2020-06-21 17:39:01 Age [y:d:h:m:s]: 04:159:18:46:03
Block: 110163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1052668 RingCT/type: yes/0
Extra: 0199a9186f4fea02c8db8243177733cd129f97343c29e8c4bb41f48fef35f77a3f02110000002b46a11e8a000000000000000000

1 output(s) for total of 264.840865183000 dcy

stealth address amount amount idx
00: 389fd3b53a1def1d0024d6c5ecfa0cacf5ed39b66867ae73ee8129e682f04f8f 264.840865183000 190795 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": 110173, "vin": [ { "gen": { "height": 110163 } } ], "vout": [ { "amount": 264840865183, "target": { "key": "389fd3b53a1def1d0024d6c5ecfa0cacf5ed39b66867ae73ee8129e682f04f8f" } } ], "extra": [ 1, 153, 169, 24, 111, 79, 234, 2, 200, 219, 130, 67, 23, 119, 51, 205, 18, 159, 151, 52, 60, 41, 232, 196, 187, 65, 244, 143, 239, 53, 247, 122, 63, 2, 17, 0, 0, 0, 43, 70, 161, 30, 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