Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd8a010fb86fbfabd5b9f443e8acf8f1e43bad023b62bc539339e9c9e7fc5ab4

Tx prefix hash: 188b82d869e0a94d3e3ade636e132cb9ca3316db314a4b486b43ffdfcfd62595
Tx public key: 838554150dc5a57861fd8f6a29b4cd3956e189c550360af553c415b5bc4eadfc
Timestamp: 1581474693 Timestamp [UCT]: 2020-02-12 02:31:33 Age [y:d:h:m:s]: 05:267:01:23:30
Block: 63165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1341365 RingCT/type: yes/0
Extra: 01838554150dc5a57861fd8f6a29b4cd3956e189c550360af553c415b5bc4eadfc021100000010026b59f3000000000000000000

1 output(s) for total of 379.060863554000 dcy

stealth address amount amount idx
00: 666fe2b0e01b682f773eda94d0430ac956c13c41bb30f095854125acc3776e65 379.060863554000 116471 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": 63175, "vin": [ { "gen": { "height": 63165 } } ], "vout": [ { "amount": 379060863554, "target": { "key": "666fe2b0e01b682f773eda94d0430ac956c13c41bb30f095854125acc3776e65" } } ], "extra": [ 1, 131, 133, 84, 21, 13, 197, 165, 120, 97, 253, 143, 106, 41, 180, 205, 57, 86, 225, 137, 197, 80, 54, 10, 245, 83, 196, 21, 181, 188, 78, 173, 252, 2, 17, 0, 0, 0, 16, 2, 107, 89, 243, 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