Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cdda847405b53284e505b9e1278f02d2a0da95d402c17e658acfe846a8c45cb3

Tx prefix hash: f133b2ac35b52f9c842457cdb381c445903356211c97ad8b2363fa3a45713911
Tx public key: 7c62cbe6d3d8b66a48a70f92db3dec8415d930384a3448162d64aff8d88ee0b1
Timestamp: 1733682948 Timestamp [UCT]: 2024-12-08 18:35:48 Age [y:d:h:m:s]: 00:119:03:09:12
Block: 1170910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84905 RingCT/type: yes/0
Extra: 017c62cbe6d3d8b66a48a70f92db3dec8415d930384a3448162d64aff8d88ee0b10211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e72df27c848626d6f8210cb8e38a339147a707a0ff6f16fcfab6cad7e45cedcf 0.600000000000 1656645 of 15

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": 1170920, "vin": [ { "gen": { "height": 1170910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e72df27c848626d6f8210cb8e38a339147a707a0ff6f16fcfab6cad7e45cedcf" } } ], "extra": [ 1, 124, 98, 203, 230, 211, 216, 182, 106, 72, 167, 15, 146, 219, 61, 236, 132, 21, 217, 48, 56, 74, 52, 72, 22, 45, 100, 175, 248, 216, 142, 224, 177, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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