Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4da398a225a7b9d673300ce548a251f888d1044c2bd81449373b7ddf8d693fc7

Tx prefix hash: 22482a7ee9f59d18426d2be4a3fbff98f33ff7e3e9aa75e321368e723d9a1263
Tx public key: 00cdbe7a3217a4d9e113fe9d09c0817fa96b1bfaf527e2b37994e1baeef46b0a
Timestamp: 1727689928 Timestamp [UCT]: 2024-09-30 09:52:08 Age [y:d:h:m:s]: 00:117:20:19:51
Block: 1121311 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84212 RingCT/type: yes/0
Extra: 0100cdbe7a3217a4d9e113fe9d09c0817fa96b1bfaf527e2b37994e1baeef46b0a021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 384ba5f347abdfc856509a81a0f4d59bba2f41acc29d20772f241976597d1fb6 0.600000000000 1603538 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": 1121321, "vin": [ { "gen": { "height": 1121311 } } ], "vout": [ { "amount": 600000000, "target": { "key": "384ba5f347abdfc856509a81a0f4d59bba2f41acc29d20772f241976597d1fb6" } } ], "extra": [ 1, 0, 205, 190, 122, 50, 23, 164, 217, 225, 19, 254, 157, 9, 192, 129, 127, 169, 107, 27, 250, 245, 39, 226, 179, 121, 148, 225, 186, 238, 244, 107, 10, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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