Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d161b7e7b9ec5c41a33f5cda0810bfb7ed0ff843ea180e060ff6c72ec99aa6e5

Tx prefix hash: a9b5a8c7ab6da6d692bfc7d006d3629bf04cefdd1f7a70754db23fec79f4ac0f
Tx public key: 0da5f989590c9fe046ef8f7dfaa2ea061d27c5cf61b8c7b98512e05d15048ec4
Timestamp: 1581993800 Timestamp [UCT]: 2020-02-18 02:43:20 Age [y:d:h:m:s]: 05:067:06:18:14
Block: 67159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1201173 RingCT/type: yes/0
Extra: 010da5f989590c9fe046ef8f7dfaa2ea061d27c5cf61b8c7b98512e05d15048ec402110000000356c366d3000000000000000000

1 output(s) for total of 367.684364160000 dcy

stealth address amount amount idx
00: a508b815f393d40d60839f1be16ab6e3748ba9730fad796f96b5a0cefbd673d9 367.684364160000 123722 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": 67169, "vin": [ { "gen": { "height": 67159 } } ], "vout": [ { "amount": 367684364160, "target": { "key": "a508b815f393d40d60839f1be16ab6e3748ba9730fad796f96b5a0cefbd673d9" } } ], "extra": [ 1, 13, 165, 249, 137, 89, 12, 159, 224, 70, 239, 143, 125, 250, 162, 234, 6, 29, 39, 197, 207, 97, 184, 199, 185, 133, 18, 224, 93, 21, 4, 142, 196, 2, 17, 0, 0, 0, 3, 86, 195, 102, 211, 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