Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdcd1d9389cdb6876feb99d8562f5e65f46d3ab0fba67cfc734b92319bdfca27

Tx prefix hash: 99206968d17a791508a9dac117f7e87591901577d55ecfadff171c3c44c707f8
Tx public key: baa2369e1acfe34e5b5d1ec0d0a047267c7ba1e60897d7a49d094ebf64e7061f
Timestamp: 1582440751 Timestamp [UCT]: 2020-02-23 06:52:31 Age [y:d:h:m:s]: 05:011:01:35:52
Block: 70771 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1161061 RingCT/type: yes/0
Extra: 01baa2369e1acfe34e5b5d1ec0d0a047267c7ba1e60897d7a49d094ebf64e7061f0211000000017adf42d3000000000000000000

1 output(s) for total of 357.690249090000 dcy

stealth address amount amount idx
00: b374d9f145d534cf8e876ab14e14fce0b4a1117d43071e1b926a0b04f513a916 357.690249090000 130739 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": 70781, "vin": [ { "gen": { "height": 70771 } } ], "vout": [ { "amount": 357690249090, "target": { "key": "b374d9f145d534cf8e876ab14e14fce0b4a1117d43071e1b926a0b04f513a916" } } ], "extra": [ 1, 186, 162, 54, 158, 26, 207, 227, 78, 91, 93, 30, 192, 208, 160, 71, 38, 124, 123, 161, 230, 8, 151, 215, 164, 157, 9, 78, 191, 100, 231, 6, 31, 2, 17, 0, 0, 0, 1, 122, 223, 66, 211, 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