Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db1c4b42ecec35763c98c8b413319cbaecb25a707e18c2352f9b64b0a51e4625

Tx prefix hash: e6528c9cf383115d1d0730379bac915d7ccc820a8406a08a4f85464a9037b6c4
Tx public key: c243f2563e8df4d73abb82365a680f2f1d1e4f3abe48d9e6636e9857195a4522
Timestamp: 1714370351 Timestamp [UCT]: 2024-04-29 05:59:11 Age [y:d:h:m:s]: 00:354:17:43:01
Block: 1010877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253605 RingCT/type: yes/0
Extra: 01c243f2563e8df4d73abb82365a680f2f1d1e4f3abe48d9e6636e9857195a452202110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 974b79c2bd1650f0e60c350755b0024138c6e880bc7e015905b616b3c65b149d 0.600000000000 1472951 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": 1010887, "vin": [ { "gen": { "height": 1010877 } } ], "vout": [ { "amount": 600000000, "target": { "key": "974b79c2bd1650f0e60c350755b0024138c6e880bc7e015905b616b3c65b149d" } } ], "extra": [ 1, 194, 67, 242, 86, 62, 141, 244, 215, 58, 187, 130, 54, 90, 104, 15, 47, 29, 30, 79, 58, 190, 72, 217, 230, 99, 110, 152, 87, 25, 90, 69, 34, 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