Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac35f9cc62ee8ef3e0724e7c915367a518c4cd0011736d4e85fb2fae1d423b8e

Tx prefix hash: a452f502aedf415a13324ce7509fb3628e4819f35f9181a30a16173688051b19
Tx public key: b0c00d72395b9a3c1a29ca0135018ad0c8eff63cfa05f9f91aab004a030691f2
Timestamp: 1651793470 Timestamp [UCT]: 2022-05-05 23:31:10 Age [y:d:h:m:s]: 02:283:15:51:37
Block: 495142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 722599 RingCT/type: yes/0
Extra: 01b0c00d72395b9a3c1a29ca0135018ad0c8eff63cfa05f9f91aab004a030691f202110000000775e3f0e9000000000000000000

1 output(s) for total of 14.040714978000 dcy

stealth address amount amount idx
00: c936ab3058ba4fa0f62cc14e81ff8ca1109839d30f117d82cee60aa5720d31f4 14.040714978000 918901 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": 495152, "vin": [ { "gen": { "height": 495142 } } ], "vout": [ { "amount": 14040714978, "target": { "key": "c936ab3058ba4fa0f62cc14e81ff8ca1109839d30f117d82cee60aa5720d31f4" } } ], "extra": [ 1, 176, 192, 13, 114, 57, 91, 154, 60, 26, 41, 202, 1, 53, 1, 138, 208, 200, 239, 246, 60, 250, 5, 249, 249, 26, 171, 0, 74, 3, 6, 145, 242, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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