Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a41044c874fc76be52d0bd2d3c8379daa19f7d1edbe9ba728fe94b3e6b6fce96

Tx prefix hash: fd361489f8bd6c2ea34c02693e65229b7db9594f07260f7e1f99fb4ccc8c0fcd
Tx public key: 60d7791f82ced10ead0609d5ec9f7831eb5754b0088f9d2cb488fafdb985e5fb
Timestamp: 1582525367 Timestamp [UCT]: 2020-02-24 06:22:47 Age [y:d:h:m:s]: 04:307:20:57:45
Block: 71614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1112408 RingCT/type: yes/0
Extra: 0160d7791f82ced10ead0609d5ec9f7831eb5754b0088f9d2cb488fafdb985e5fb0211000000038a2ee0d9000000000000000000

1 output(s) for total of 355.429759197000 dcy

stealth address amount amount idx
00: 43fd2f647b899016bf4e71a472b40faccbbc70c1364b9ea90e434b3e4a369bd0 355.429759197000 132209 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": 71624, "vin": [ { "gen": { "height": 71614 } } ], "vout": [ { "amount": 355429759197, "target": { "key": "43fd2f647b899016bf4e71a472b40faccbbc70c1364b9ea90e434b3e4a369bd0" } } ], "extra": [ 1, 96, 215, 121, 31, 130, 206, 209, 14, 173, 6, 9, 213, 236, 159, 120, 49, 235, 87, 84, 176, 8, 143, 157, 44, 180, 136, 250, 253, 185, 133, 229, 251, 2, 17, 0, 0, 0, 3, 138, 46, 224, 217, 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