Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c29645bd2269596839c169eb909337521f5ea07bf92a38f586b4d5ac233166a

Tx prefix hash: cf928eabe4b123cc2a494fd7db1b3973a9e7b0aa29a80cdab13c0a784730518f
Tx public key: c6a4a79d8b5b4681aed23f1772abcd9c35f78cba18652cfb0ac7140cb0f314e6
Timestamp: 1755540836 Timestamp [UCT]: 2025-08-18 18:13:56 Age [y:d:h:m:s]: 00:089:08:14:14
Block: 1349352 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63727 RingCT/type: yes/0
Extra: 01c6a4a79d8b5b4681aed23f1772abcd9c35f78cba18652cfb0ac7140cb0f314e6021100000003a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e002ce395502d6a573e62682831edde13078f7b841de603a65e0623cd8a5d337 0.600000000000 1837283 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": 1349362, "vin": [ { "gen": { "height": 1349352 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e002ce395502d6a573e62682831edde13078f7b841de603a65e0623cd8a5d337" } } ], "extra": [ 1, 198, 164, 167, 157, 139, 91, 70, 129, 174, 210, 63, 23, 114, 171, 205, 156, 53, 247, 140, 186, 24, 101, 44, 251, 10, 199, 20, 12, 176, 243, 20, 230, 2, 17, 0, 0, 0, 3, 161, 29, 186, 152, 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