Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 163945a557496cc17ddfd49d83506581cae26b8394fd48bcee0d9480ac8d4560

Tx prefix hash: da5bb7e92a8bf576c182c91a337995f1315433c3c622f52b67c536e98b08e4b0
Tx public key: 40c2d9e13b6fb4982f506fc563e7f101471d3de0317850d17d1a70f6809fd2f9
Timestamp: 1709353346 Timestamp [UCT]: 2024-03-02 04:22:26 Age [y:d:h:m:s]: 01:046:15:02:58
Block: 969298 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294319 RingCT/type: yes/0
Extra: 0140c2d9e13b6fb4982f506fc563e7f101471d3de0317850d17d1a70f6809fd2f90211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 648b16b1298a867dfcf9faafe333649efa962896bff7ad11536e6f2421297124 0.600000000000 1429127 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": 969308, "vin": [ { "gen": { "height": 969298 } } ], "vout": [ { "amount": 600000000, "target": { "key": "648b16b1298a867dfcf9faafe333649efa962896bff7ad11536e6f2421297124" } } ], "extra": [ 1, 64, 194, 217, 225, 59, 111, 180, 152, 47, 80, 111, 197, 99, 231, 241, 1, 71, 29, 61, 224, 49, 120, 80, 209, 125, 26, 112, 246, 128, 159, 210, 249, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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