Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfa65a7c9dab143b3de8f31a49ff0a103bfe7ec48fc33f342e1229b9dcc7ba53

Tx prefix hash: 9a328593ad655f40604fdb5d00f4ef1b067b55a1c48571f7ca8e530fbad81acd
Tx public key: 068c492950a206aa21c42ce3c77b33b1feb2aa053b7cd7614a22627f54110d89
Timestamp: 1712958022 Timestamp [UCT]: 2024-04-12 21:40:22 Age [y:d:h:m:s]: 00:225:15:54:04
Block: 999152 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161565 RingCT/type: yes/0
Extra: 01068c492950a206aa21c42ce3c77b33b1feb2aa053b7cd7614a22627f54110d890211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f95cf15b4465fe1b06857e9e96471363a9626d2c12fdffe54c1f871ad45ff717 0.600000000000 1459630 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": 999162, "vin": [ { "gen": { "height": 999152 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f95cf15b4465fe1b06857e9e96471363a9626d2c12fdffe54c1f871ad45ff717" } } ], "extra": [ 1, 6, 140, 73, 41, 80, 162, 6, 170, 33, 196, 44, 227, 199, 123, 51, 177, 254, 178, 170, 5, 59, 124, 215, 97, 74, 34, 98, 127, 84, 17, 13, 137, 2, 17, 0, 0, 0, 7, 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