Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a3c20d2f11a6c77bfa72bd2ba19c85e3df45d1cbaa2aa383e7b48426d6f9487

Tx prefix hash: 8786d6eba7032dd581bece657964bc6a9675fde39cb748318aa4ae5adf43a06c
Tx public key: d0abc9fc61676e952e8bd605f1d85c53efa5fa7a908decf5bc7714ba21fa01e7
Timestamp: 1710395474 Timestamp [UCT]: 2024-03-14 05:51:14 Age [y:d:h:m:s]: 01:097:18:50:12
Block: 977946 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330767 RingCT/type: yes/0
Extra: 01d0abc9fc61676e952e8bd605f1d85c53efa5fa7a908decf5bc7714ba21fa01e702110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 75be075173536fdf7c86e4d5965ac56ea784c0368cb99a49daba582beef51230 0.600000000000 1437955 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": 977956, "vin": [ { "gen": { "height": 977946 } } ], "vout": [ { "amount": 600000000, "target": { "key": "75be075173536fdf7c86e4d5965ac56ea784c0368cb99a49daba582beef51230" } } ], "extra": [ 1, 208, 171, 201, 252, 97, 103, 110, 149, 46, 139, 214, 5, 241, 216, 92, 83, 239, 165, 250, 122, 144, 141, 236, 245, 188, 119, 20, 186, 33, 250, 1, 231, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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