Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b576b1bbeeb4e83e4141783d3f4feb3e82dbf07ca15c4bbc2141301cc7f9505

Tx prefix hash: 47bd285aa0149d7458286774d6cef0089b37d533e2a6b64c9d745bd1265ed578
Tx public key: e3fd51d2c26412bb1ec0e5146272c33da56e8b134a0d1ecb251d947bd207f079
Timestamp: 1713272746 Timestamp [UCT]: 2024-04-16 13:05:46 Age [y:d:h:m:s]: 01:228:22:59:26
Block: 1001764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 422342 RingCT/type: yes/0
Extra: 01e3fd51d2c26412bb1ec0e5146272c33da56e8b134a0d1ecb251d947bd207f0790211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4cfe97ddff556c9ac646aa29383650b4189429ad7ddf5339165468a49c157d5d 0.600000000000 1462276 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": 1001774, "vin": [ { "gen": { "height": 1001764 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4cfe97ddff556c9ac646aa29383650b4189429ad7ddf5339165468a49c157d5d" } } ], "extra": [ 1, 227, 253, 81, 210, 194, 100, 18, 187, 30, 192, 229, 20, 98, 114, 195, 61, 165, 110, 139, 19, 74, 13, 30, 203, 37, 29, 148, 123, 210, 7, 240, 121, 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