Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84dd75d1fe6b0cee666a73d7a249757d91a33dd96a80a747d1ad7a143c8a7fa3

Tx prefix hash: b08affc0de467038f49e30a59d8528c9409aa99ac3ac6c313476bb2a6342f317
Tx public key: 0a772bc37dc5f4cc3e2420d955c815711d689afa720d3582c171d392ea21fea0
Timestamp: 1581822401 Timestamp [UCT]: 2020-02-16 03:06:41 Age [y:d:h:m:s]: 04:359:15:06:18
Block: 65814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1149150 RingCT/type: yes/0
Extra: 010a772bc37dc5f4cc3e2420d955c815711d689afa720d3582c171d392ea21fea0021100000001c71d3ff9000000000000000000

1 output(s) for total of 371.476809715000 dcy

stealth address amount amount idx
00: 1157b44f846e870f27227192ab1c658d0b5329cf913c8e07d9ef8ae9d0426992 371.476809715000 121417 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": 65824, "vin": [ { "gen": { "height": 65814 } } ], "vout": [ { "amount": 371476809715, "target": { "key": "1157b44f846e870f27227192ab1c658d0b5329cf913c8e07d9ef8ae9d0426992" } } ], "extra": [ 1, 10, 119, 43, 195, 125, 197, 244, 204, 62, 36, 32, 217, 85, 200, 21, 113, 29, 104, 154, 250, 114, 13, 53, 130, 193, 113, 211, 146, 234, 33, 254, 160, 2, 17, 0, 0, 0, 1, 199, 29, 63, 249, 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