Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: caff7e0504f31a45e9d5ce4b3d90c539cfd7a1b242f9b4e5f2a71888971c7176

Tx prefix hash: e4a13291a2f1e4fb1fc0694eb13fd1b97049d74568ac60907e873825245f8b9e
Tx public key: e4aba6854e830af03e13dd7315d3e52317d141c0872d0de2aa5d86062e9c7e0d
Timestamp: 1699240952 Timestamp [UCT]: 2023-11-06 03:22:32 Age [y:d:h:m:s]: 01:150:11:08:17
Block: 885446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0811 kB
Tx version: 2 No of confirmations: 368740 RingCT/type: yes/0
Extra: 01e4aba6854e830af03e13dd7315d3e52317d141c0872d0de2aa5d86062e9c7e0d

1 output(s) for total of 0.714742885000 dcy

stealth address amount amount idx
00: d92620e747f9b936b3c5b6263e0600bb1f020e0ae4df28e13f82a1d3b4fde944 0.714742885000 1341215 of 0

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": 885456, "vin": [ { "gen": { "height": 885446 } } ], "vout": [ { "amount": 714742885, "target": { "key": "d92620e747f9b936b3c5b6263e0600bb1f020e0ae4df28e13f82a1d3b4fde944" } } ], "extra": [ 1, 228, 171, 166, 133, 78, 131, 10, 240, 62, 19, 221, 115, 21, 211, 229, 35, 23, 209, 65, 192, 135, 45, 13, 226, 170, 93, 134, 6, 46, 156, 126, 13 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8