Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c27df0605502a3298155884c61db158b28de1ee38c50e8d379438d3f4b809ba

Tx prefix hash: 5ef4972f7a8122562253c94edffff34d00333cfef52ffcd1544cbde09f2af2d3
Tx public key: 1d46ad4b1b322e1b3bf4f33904b652e388762e456d85c32869557a3415a7e492
Timestamp: 1580979410 Timestamp [UCT]: 2020-02-06 08:56:50 Age [y:d:h:m:s]: 05:085:03:44:03
Block: 59856 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1212871 RingCT/type: yes/0
Extra: 011d46ad4b1b322e1b3bf4f33904b652e388762e456d85c32869557a3415a7e49202110000000703d36d11000000000000000000

1 output(s) for total of 388.752364134000 dcy

stealth address amount amount idx
00: ef86dc87621084a4d73d082d9444554b4a43da4fcd2fbd4d9b2a8feb2f42f1bf 388.752364134000 110384 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": 59866, "vin": [ { "gen": { "height": 59856 } } ], "vout": [ { "amount": 388752364134, "target": { "key": "ef86dc87621084a4d73d082d9444554b4a43da4fcd2fbd4d9b2a8feb2f42f1bf" } } ], "extra": [ 1, 29, 70, 173, 75, 27, 50, 46, 27, 59, 244, 243, 57, 4, 182, 82, 227, 136, 118, 46, 69, 109, 133, 195, 40, 105, 85, 122, 52, 21, 167, 228, 146, 2, 17, 0, 0, 0, 7, 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