Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18fd2a71b2d12417c8f22035e31a41af37ed6c840c86d79b8c731c714b7cf1b8

Tx prefix hash: 790d09602ba656dc48e898f9757bf695ce294812e88bccaf32ba4a5a135293fc
Tx public key: d85f402400fdbae329e738896c0b1be6fab98e31c63448aec7329791848be0ae
Timestamp: 1581946695 Timestamp [UCT]: 2020-02-17 13:38:15 Age [y:d:h:m:s]: 04:362:18:06:07
Block: 66674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1151558 RingCT/type: yes/0
Extra: 01d85f402400fdbae329e738896c0b1be6fab98e31c63448aec7329791848be0ae0211000000010aca7173000000000000000000

1 output(s) for total of 369.047416027000 dcy

stealth address amount amount idx
00: 6eb1fcdc903c1345a6de4c88b94e6d43a068ea6489622381cf41f103b865285e 369.047416027000 122835 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": 66684, "vin": [ { "gen": { "height": 66674 } } ], "vout": [ { "amount": 369047416027, "target": { "key": "6eb1fcdc903c1345a6de4c88b94e6d43a068ea6489622381cf41f103b865285e" } } ], "extra": [ 1, 216, 95, 64, 36, 0, 253, 186, 227, 41, 231, 56, 137, 108, 11, 27, 230, 250, 185, 142, 49, 198, 52, 72, 174, 199, 50, 151, 145, 132, 139, 224, 174, 2, 17, 0, 0, 0, 1, 10, 202, 113, 115, 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