Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 352e1bf1d4c17bbce74d2e174e3c2c7e8b265dbdb70ec474b6a3a6614a98e5fd

Tx prefix hash: 22b90ccb4b81971e1698d8ae7905663453d1a43509f68cd8fe45a75c3dc2649e
Tx public key: 856311cef3020b892d6184af110db4dfab64f888139a7e1bf6c78e273dd3ce3f
Timestamp: 1732037406 Timestamp [UCT]: 2024-11-19 17:30:06 Age [y:d:h:m:s]: 00:158:17:06:48
Block: 1157265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113257 RingCT/type: yes/0
Extra: 01856311cef3020b892d6184af110db4dfab64f888139a7e1bf6c78e273dd3ce3f0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aebfd3b5d5fd0436f389fd0916819af006144eb128628d6bd6849e0454b7a492 0.600000000000 1642888 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": 1157275, "vin": [ { "gen": { "height": 1157265 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aebfd3b5d5fd0436f389fd0916819af006144eb128628d6bd6849e0454b7a492" } } ], "extra": [ 1, 133, 99, 17, 206, 243, 2, 11, 137, 45, 97, 132, 175, 17, 13, 180, 223, 171, 100, 248, 136, 19, 154, 126, 27, 246, 199, 142, 39, 61, 211, 206, 63, 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