Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea6926ccfa4e0feceefa8190eeef7046786ad1ae705b27210ac1729d348c35e2

Tx prefix hash: 9646d7763cb0671d7f9b3efba08863a20d93760be82aa8bcf7fe6a76f6f28656
Tx public key: 51fdeb8e896eced9f8881ae7f431c1bbcf6dd734b50599ee0697a7cf1be41bda
Timestamp: 1740563374 Timestamp [UCT]: 2025-02-26 09:49:34 Age [y:d:h:m:s]: 00:015:15:13:33
Block: 1227568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11212 RingCT/type: yes/0
Extra: 0151fdeb8e896eced9f8881ae7f431c1bbcf6dd734b50599ee0697a7cf1be41bda0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e6d0e4036b6c9c9f80929fff1c3f38a5a3fea9bcc4cc9a52ef61b4bd8b95bd3 0.600000000000 1714443 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": 1227578, "vin": [ { "gen": { "height": 1227568 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e6d0e4036b6c9c9f80929fff1c3f38a5a3fea9bcc4cc9a52ef61b4bd8b95bd3" } } ], "extra": [ 1, 81, 253, 235, 142, 137, 110, 206, 217, 248, 136, 26, 231, 244, 49, 193, 187, 207, 109, 215, 52, 181, 5, 153, 238, 6, 151, 167, 207, 27, 228, 27, 218, 2, 17, 0, 0, 0, 2, 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