Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5cff560cafb619f6f7703a699af26d39a0e498ddb1177864b7567ef4bc798817

Tx prefix hash: 4fce84c4d67e78ab285bf833bc1f8be965e99f380062d2d0b5c733fe1a51e2b1
Tx public key: 788910473383c3c3222f98e06002fcecac1e8af175e9524cec66f91d7c75c900
Timestamp: 1702683669 Timestamp [UCT]: 2023-12-15 23:41:09 Age [y:d:h:m:s]: 01:116:23:08:44
Block: 913986 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344733 RingCT/type: yes/0
Extra: 01788910473383c3c3222f98e06002fcecac1e8af175e9524cec66f91d7c75c90002110000000375e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8e6519a1fd0c1f86898ef3645b51bb9b1682ac54d75ab0d0d102dc8a2f4f280 0.600000000000 1371266 of 15

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": 913996, "vin": [ { "gen": { "height": 913986 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8e6519a1fd0c1f86898ef3645b51bb9b1682ac54d75ab0d0d102dc8a2f4f280" } } ], "extra": [ 1, 120, 137, 16, 71, 51, 131, 195, 195, 34, 47, 152, 224, 96, 2, 252, 236, 172, 30, 138, 241, 117, 233, 82, 76, 236, 102, 249, 29, 124, 117, 201, 0, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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