Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ba1eb9bf5605bae22bf6d41962c9becaad3559b1129789cc2a9c6a54b527b97

Tx prefix hash: d1b8af02d9cc820d86643d18d690b069c79f1ce483e1194459e492054dc1b6c3
Tx public key: 7dfb0b643d0e016645c7948dae9fc3417e371f189ded953504686f969cb8e4e8
Timestamp: 1583458161 Timestamp [UCT]: 2020-03-06 01:29:21 Age [y:d:h:m:s]: 04:295:06:43:47
Block: 77266 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1105487 RingCT/type: yes/0
Extra: 017dfb0b643d0e016645c7948dae9fc3417e371f189ded953504686f969cb8e4e802110000000dd81c26c0000000000000000000

1 output(s) for total of 340.397577986000 dcy

stealth address amount amount idx
00: ddcc95de14a9e17b96cb288d105f371bf1ad97a0c0a97925af4cd7000fd33f24 340.397577986000 142171 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": 77276, "vin": [ { "gen": { "height": 77266 } } ], "vout": [ { "amount": 340397577986, "target": { "key": "ddcc95de14a9e17b96cb288d105f371bf1ad97a0c0a97925af4cd7000fd33f24" } } ], "extra": [ 1, 125, 251, 11, 100, 61, 14, 1, 102, 69, 199, 148, 141, 174, 159, 195, 65, 126, 55, 31, 24, 157, 237, 149, 53, 4, 104, 111, 150, 156, 184, 228, 232, 2, 17, 0, 0, 0, 13, 216, 28, 38, 192, 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