Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9be0c7c4bdf8bf62ef59762d31a9814080ae98e49c4f165cbc4aa045e389e3da

Tx prefix hash: 7d6861d6df9229ae7dd53fa88e90fa77e4b0c73990ee04a45f0a180af6295946
Tx public key: fcbc5bfd17cc9362bfd009251352638eed5f3b5a9352335efc9e858230ddc293
Timestamp: 1582387015 Timestamp [UCT]: 2020-02-22 15:56:55 Age [y:d:h:m:s]: 04:310:02:23:03
Block: 70304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1114159 RingCT/type: yes/0
Extra: 01fcbc5bfd17cc9362bfd009251352638eed5f3b5a9352335efc9e858230ddc2930211000000017adf42d3000000000000000000

1 output(s) for total of 358.981061342000 dcy

stealth address amount amount idx
00: 4a91dfc3c581f8197206fca15e1c21b8e9586e13ad9b19039883be21b4ed3d62 358.981061342000 129849 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": 70314, "vin": [ { "gen": { "height": 70304 } } ], "vout": [ { "amount": 358981061342, "target": { "key": "4a91dfc3c581f8197206fca15e1c21b8e9586e13ad9b19039883be21b4ed3d62" } } ], "extra": [ 1, 252, 188, 91, 253, 23, 204, 147, 98, 191, 208, 9, 37, 19, 82, 99, 142, 237, 95, 59, 90, 147, 82, 51, 94, 252, 158, 133, 130, 48, 221, 194, 147, 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