Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3c075a57bf06486f36c3250650b3b351b16a547c10f225d96d9b61817b4cfbe

Tx prefix hash: caae615c3d969d3b41686fc04b36e434f7d99af314a2fc9636d6c3bd1b9d4321
Tx public key: a83644ba5933f7e7137dff71c0531722094c222ae22474566b1cd46e33ef7617
Timestamp: 1697245653 Timestamp [UCT]: 2023-10-14 01:07:33 Age [y:d:h:m:s]: 01:098:10:27:59
Block: 869113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331568 RingCT/type: yes/0
Extra: 01a83644ba5933f7e7137dff71c0531722094c222ae22474566b1cd46e33ef761702110000000a33af99f4000000000000000000

1 output(s) for total of 0.809595105000 dcy

stealth address amount amount idx
00: ca7b541c86f60228b284872ced4c1a6d3de349b5ba46f8d36414a1137a416f6e 0.809595105000 1323948 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": 869123, "vin": [ { "gen": { "height": 869113 } } ], "vout": [ { "amount": 809595105, "target": { "key": "ca7b541c86f60228b284872ced4c1a6d3de349b5ba46f8d36414a1137a416f6e" } } ], "extra": [ 1, 168, 54, 68, 186, 89, 51, 247, 231, 19, 125, 255, 113, 192, 83, 23, 34, 9, 76, 34, 42, 226, 36, 116, 86, 107, 28, 212, 110, 51, 239, 118, 23, 2, 17, 0, 0, 0, 10, 51, 175, 153, 244, 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