Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a8c17207ffb176df1441f4434bece8b64fa7fc207156c29ea332dd4e4d4b71e

Tx prefix hash: 7d4e9bb736e3a5da2f9f5b16d90078cbe7247eed6bc947bb3089dd285c37d116
Tx public key: 453d96db41aa5805d6cce8d83b00ce3556b3e61e80d6037576bbca58091e77d2
Timestamp: 1719241934 Timestamp [UCT]: 2024-06-24 15:12:14 Age [y:d:h:m:s]: 00:285:00:17:54
Block: 1051252 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203673 RingCT/type: yes/0
Extra: 01453d96db41aa5805d6cce8d83b00ce3556b3e61e80d6037576bbca58091e77d202110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d59ef1ccc64c184df5f97a069b8f7f492900cc60aa5d1508b5c7a49f094cf70 0.600000000000 1521561 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": 1051262, "vin": [ { "gen": { "height": 1051252 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d59ef1ccc64c184df5f97a069b8f7f492900cc60aa5d1508b5c7a49f094cf70" } } ], "extra": [ 1, 69, 61, 150, 219, 65, 170, 88, 5, 214, 204, 232, 216, 59, 0, 206, 53, 86, 179, 230, 30, 128, 214, 3, 117, 118, 187, 202, 88, 9, 30, 119, 210, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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