Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6743f690f1807c656afe1bee856fde68aece868406ef4245764277899beec7e6

Tx prefix hash: a5a03ceeff650f49d574bc825ddbe565acbdb05be1a57dc2ade8b79691c0419b
Tx public key: 0fc79672607297c6caa336a1be73d67326b0c5b3f4bcebd2b5cc0883d6bfb3c8
Timestamp: 1581704214 Timestamp [UCT]: 2020-02-14 18:16:54 Age [y:d:h:m:s]: 04:360:10:09:10
Block: 65281 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1149264 RingCT/type: yes/0
Extra: 010fc79672607297c6caa336a1be73d67326b0c5b3f4bcebd2b5cc0883d6bfb3c802110000000403d36d11000000000000000000

1 output(s) for total of 372.990489361000 dcy

stealth address amount amount idx
00: f416f79294484812fbf29be1ec27ccc114d371964eb6c4fecfcc8e1fd4d079d7 372.990489361000 120312 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": 65291, "vin": [ { "gen": { "height": 65281 } } ], "vout": [ { "amount": 372990489361, "target": { "key": "f416f79294484812fbf29be1ec27ccc114d371964eb6c4fecfcc8e1fd4d079d7" } } ], "extra": [ 1, 15, 199, 150, 114, 96, 114, 151, 198, 202, 163, 54, 161, 190, 115, 214, 115, 38, 176, 197, 179, 244, 188, 235, 210, 181, 204, 8, 131, 214, 191, 179, 200, 2, 17, 0, 0, 0, 4, 3, 211, 109, 17, 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