Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e52dcb355a097f07d1f8e580ec8d5a9ba53ba55398ce85b3e9a908d523813e2

Tx prefix hash: 0415827564e84b39077ab26213111f72d5a20838e6547530ff4980a0c8cba199
Tx public key: e258ec3b79d6530d30e1f4e9f22e7b6a5b8f1d78514d7cf3a568dfa0ad1f6e6c
Timestamp: 1709008215 Timestamp [UCT]: 2024-02-27 04:30:15 Age [y:d:h:m:s]: 01:060:22:55:46
Block: 966432 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304596 RingCT/type: yes/0
Extra: 01e258ec3b79d6530d30e1f4e9f22e7b6a5b8f1d78514d7cf3a568dfa0ad1f6e6c0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5747706dfe499b5110386423a3f30099bf46c71e2039512d6926a6c662387a33 0.600000000000 1426189 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": 966442, "vin": [ { "gen": { "height": 966432 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5747706dfe499b5110386423a3f30099bf46c71e2039512d6926a6c662387a33" } } ], "extra": [ 1, 226, 88, 236, 59, 121, 214, 83, 13, 48, 225, 244, 233, 242, 46, 123, 106, 91, 143, 29, 120, 81, 77, 124, 243, 165, 104, 223, 160, 173, 31, 110, 108, 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