Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: debcc2a06f1821c4f592fc313cb35874bb56d3451d889c17d69182d1b7a107f1

Tx prefix hash: cb1c96d08e1a4dafb07aa4cc98c3aa18b992c1e23ddf7ad35f07b673de27f959
Tx public key: 270afe037ecaa8ae9618c82b74c7cf10958ffb86c05ec9fee311248364f30941
Timestamp: 1634544830 Timestamp [UCT]: 2021-10-18 08:13:50 Age [y:d:h:m:s]: 03:112:13:43:41
Block: 355466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 858174 RingCT/type: yes/0
Extra: 01270afe037ecaa8ae9618c82b74c7cf10958ffb86c05ec9fee311248364f309410211000000118d0de867000000000000000000

1 output(s) for total of 40.756229267000 dcy

stealth address amount amount idx
00: e9eaee11bcc9c4e1b7ca84843dc44855833eb15b1e132bf733a73ae7b50985bb 40.756229267000 725684 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": 355476, "vin": [ { "gen": { "height": 355466 } } ], "vout": [ { "amount": 40756229267, "target": { "key": "e9eaee11bcc9c4e1b7ca84843dc44855833eb15b1e132bf733a73ae7b50985bb" } } ], "extra": [ 1, 39, 10, 254, 3, 126, 202, 168, 174, 150, 24, 200, 43, 116, 199, 207, 16, 149, 143, 251, 134, 192, 94, 201, 254, 227, 17, 36, 131, 100, 243, 9, 65, 2, 17, 0, 0, 0, 17, 141, 13, 232, 103, 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