Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfa549beb2b493997fde746d6bd33c5235e7f98d4d43233f4b270123f2adfb64

Tx prefix hash: 894c9cc0ba648ade172eec98ac6718959dc9beb112ff60e975a788333957d7f1
Tx public key: 32d3319970d3811f33ab7bcaadbb147cf325c59d3ffd0b5164156d44517c80a6
Timestamp: 1685539245 Timestamp [UCT]: 2023-05-31 13:20:45 Age [y:d:h:m:s]: 01:310:14:04:57
Block: 772111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 483166 RingCT/type: yes/0
Extra: 0132d3319970d3811f33ab7bcaadbb147cf325c59d3ffd0b5164156d44517c80a6021100000004faf35c9c000000000000000000

1 output(s) for total of 1.696976817000 dcy

stealth address amount amount idx
00: c6e9ebca9e8fde7434315cbc3e97ad97d0340251ae8f0c3ba5ae12d81f3ca46d 1.696976817000 1221502 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": 772121, "vin": [ { "gen": { "height": 772111 } } ], "vout": [ { "amount": 1696976817, "target": { "key": "c6e9ebca9e8fde7434315cbc3e97ad97d0340251ae8f0c3ba5ae12d81f3ca46d" } } ], "extra": [ 1, 50, 211, 49, 153, 112, 211, 129, 31, 51, 171, 123, 202, 173, 187, 20, 124, 243, 37, 197, 157, 63, 253, 11, 81, 100, 21, 109, 68, 81, 124, 128, 166, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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