Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac4b66f7d8d8731cc4730dc1ef0a3b31b7cf5672a44f2d2c687cda2e20be0c46

Tx prefix hash: bffb57e78c7f854a713208da443d6f3ed2299543622f2a5fb18a35aa85bae373
Tx public key: cdf9962ef2221fbfff763665d60aff65aab201b7e6e9a47e8825851dca970807
Timestamp: 1714645165 Timestamp [UCT]: 2024-05-02 10:19:25 Age [y:d:h:m:s]: 00:341:10:23:44
Block: 1013162 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244062 RingCT/type: yes/0
Extra: 01cdf9962ef2221fbfff763665d60aff65aab201b7e6e9a47e8825851dca9708070211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60f403aa0c1f3c4336e3ff0eb21812f8aa9bf139d559428267c55bfc9e1febf6 0.600000000000 1475905 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": 1013172, "vin": [ { "gen": { "height": 1013162 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60f403aa0c1f3c4336e3ff0eb21812f8aa9bf139d559428267c55bfc9e1febf6" } } ], "extra": [ 1, 205, 249, 150, 46, 242, 34, 31, 191, 255, 118, 54, 101, 214, 10, 255, 101, 170, 178, 1, 183, 230, 233, 164, 126, 136, 37, 133, 29, 202, 151, 8, 7, 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