Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ca5a6724a07a0ee588cc48c91f65dc76212f0532e8fd9cf0bc6e62f5883c66a

Tx prefix hash: ca08450a151013228e7f8a812182692ac113cab522b67aaa270986425cbdc744
Tx public key: f73ac883eb351bd1cab90cda15aa8c4a29ea67193bda1cb6ab36a07ff8ed7e7e
Timestamp: 1718188796 Timestamp [UCT]: 2024-06-12 10:39:56 Age [y:d:h:m:s]: 00:226:14:14:41
Block: 1042546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162114 RingCT/type: yes/0
Extra: 01f73ac883eb351bd1cab90cda15aa8c4a29ea67193bda1cb6ab36a07ff8ed7e7e0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41c9dac9678e56180b49e13eab70edc375c10fa2aecf67fd1e51147503a45686 0.600000000000 1511491 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": 1042556, "vin": [ { "gen": { "height": 1042546 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41c9dac9678e56180b49e13eab70edc375c10fa2aecf67fd1e51147503a45686" } } ], "extra": [ 1, 247, 58, 200, 131, 235, 53, 27, 209, 202, 185, 12, 218, 21, 170, 140, 74, 41, 234, 103, 25, 59, 218, 28, 182, 171, 54, 160, 127, 248, 237, 126, 126, 2, 17, 0, 0, 0, 4, 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