Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f50baef2b9c4c8def234eaafa629176e014977015d0348e408a2e5096f4f8b9

Tx prefix hash: 7e02d0f9f0758fac41a6069fcef0ec5c53528572a36badc52ed3ab646f5a912b
Tx public key: 0a97f49c4660dde6a263926bfec11cc9d3b4c152f6fa07eea7c97608a2544d68
Timestamp: 1753710629 Timestamp [UCT]: 2025-07-28 13:50:29 Age [y:d:h:m:s]: 00:073:01:32:30
Block: 1335254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50994 RingCT/type: yes/0
Extra: 010a97f49c4660dde6a263926bfec11cc9d3b4c152f6fa07eea7c97608a2544d6802110000000fef221485000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c404db0084bdd80fd03d00c5d463415a01e1b25913f29169f6483e4b06679ad0 0.600000000000 1823055 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": 1335264, "vin": [ { "gen": { "height": 1335254 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c404db0084bdd80fd03d00c5d463415a01e1b25913f29169f6483e4b06679ad0" } } ], "extra": [ 1, 10, 151, 244, 156, 70, 96, 221, 230, 162, 99, 146, 107, 254, 193, 28, 201, 211, 180, 193, 82, 246, 250, 7, 238, 167, 201, 118, 8, 162, 84, 77, 104, 2, 17, 0, 0, 0, 15, 239, 34, 20, 133, 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