Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd6130b2567c6690c5fb6354c4869aff73e762c10f692e5c846da14b29da7b7d

Tx prefix hash: 9694b88a296e57db056ef9a3c34be6916c859b95ffc9859264c896a84a1b1474
Tx public key: 2b9fbe061ffdadbaf5c382e42d83031d334aa864756034321649c0d76442518d
Timestamp: 1696584722 Timestamp [UCT]: 2023-10-06 09:32:02 Age [y:d:h:m:s]: 01:221:15:44:22
Block: 863632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419488 RingCT/type: yes/0
Extra: 012b9fbe061ffdadbaf5c382e42d83031d334aa864756034321649c0d76442518d02110000000333af99f4000000000000000000

1 output(s) for total of 0.844167659000 dcy

stealth address amount amount idx
00: 45aeb754c4965cfa015d6777ed733e48866db30c3f8f76bb65af5c4cb9364e9e 0.844167659000 1318102 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": 863642, "vin": [ { "gen": { "height": 863632 } } ], "vout": [ { "amount": 844167659, "target": { "key": "45aeb754c4965cfa015d6777ed733e48866db30c3f8f76bb65af5c4cb9364e9e" } } ], "extra": [ 1, 43, 159, 190, 6, 31, 253, 173, 186, 245, 195, 130, 228, 45, 131, 3, 29, 51, 74, 168, 100, 117, 96, 52, 50, 22, 73, 192, 215, 100, 66, 81, 141, 2, 17, 0, 0, 0, 3, 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