Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9d14fb04975813b1ba9fac2ccfc5eb1d1296bf8d95922b0e4c6b466f9dc55cf

Tx prefix hash: 5bb7ca46f59db419dbb410b5ef1447b28ad9d4b408d223c905d39175bfd74c76
Tx public key: d42fc1de34e4867264eb78d2edc923fb55cbf04c6be996fbc889130f3fac040e
Timestamp: 1720190153 Timestamp [UCT]: 2024-07-05 14:35:53 Age [y:d:h:m:s]: 00:315:01:34:59
Block: 1059130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225146 RingCT/type: yes/0
Extra: 01d42fc1de34e4867264eb78d2edc923fb55cbf04c6be996fbc889130f3fac040e0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6219fcae8e9adff2f1031423d3da7b300d4efa0c0828bbe5156458e56edb5dc4 0.600000000000 1529591 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": 1059140, "vin": [ { "gen": { "height": 1059130 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6219fcae8e9adff2f1031423d3da7b300d4efa0c0828bbe5156458e56edb5dc4" } } ], "extra": [ 1, 212, 47, 193, 222, 52, 228, 134, 114, 100, 235, 120, 210, 237, 201, 35, 251, 85, 203, 240, 76, 107, 233, 150, 251, 200, 137, 19, 15, 63, 172, 4, 14, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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