Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 450f5e5653ee1529acc6b61aa4df7ae0cc7465b8f3ee3a933808ccc93a6fef63

Tx prefix hash: 65cf3f430ad96c2134559d2a3bd64f96c82b30c5b935a6052388acc34b510c09
Tx public key: de72cd6714b78dd28571069c18dd099aa5bb9af1f3842efe7fe13a36f61a90e5
Timestamp: 1714651322 Timestamp [UCT]: 2024-05-02 12:02:02 Age [y:d:h:m:s]: 00:250:04:44:01
Block: 1013217 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179074 RingCT/type: yes/0
Extra: 01de72cd6714b78dd28571069c18dd099aa5bb9af1f3842efe7fe13a36f61a90e50211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f61e37bc8bf41f66d37684489ee411e314be99380e8da396bcd9ed3c88bac43 0.600000000000 1475976 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": 1013227, "vin": [ { "gen": { "height": 1013217 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f61e37bc8bf41f66d37684489ee411e314be99380e8da396bcd9ed3c88bac43" } } ], "extra": [ 1, 222, 114, 205, 103, 20, 183, 141, 210, 133, 113, 6, 156, 24, 221, 9, 154, 165, 187, 154, 241, 243, 132, 46, 254, 127, 225, 58, 54, 246, 26, 144, 229, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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