Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7eb6ee953f5a5b572a344c6a2490eba2166eee34de0cc44e16b81b19048b995

Tx prefix hash: 13bf6bf1bc3015963ce2c8c7d6d7e1407919b64d3577423a4abed3e4fdf497fd
Tx public key: fb262584c7f000e6637f8a74c4b403209e7b528c67e72adf18d0d22a5921cd2a
Timestamp: 1581705894 Timestamp [UCT]: 2020-02-14 18:44:54 Age [y:d:h:m:s]: 05:087:11:25:51
Block: 65354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1215047 RingCT/type: yes/0
Extra: 01fb262584c7f000e6637f8a74c4b403209e7b528c67e72adf18d0d22a5921cd2a021100000001724f989b000000000000000000

1 output(s) for total of 372.782810921000 dcy

stealth address amount amount idx
00: c4fa8a12763b360699e9cac94af3b881a933fc8c1ea645ea837bf2adc6315d1d 372.782810921000 120421 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": 65364, "vin": [ { "gen": { "height": 65354 } } ], "vout": [ { "amount": 372782810921, "target": { "key": "c4fa8a12763b360699e9cac94af3b881a933fc8c1ea645ea837bf2adc6315d1d" } } ], "extra": [ 1, 251, 38, 37, 132, 199, 240, 0, 230, 99, 127, 138, 116, 196, 180, 3, 32, 158, 123, 82, 140, 103, 231, 42, 223, 24, 208, 210, 42, 89, 33, 205, 42, 2, 17, 0, 0, 0, 1, 114, 79, 152, 155, 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