Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8144412295d35f549f9e166b6826dca8a30eb7f0315ac1c1ed102fbc2da274c3

Tx prefix hash: 4867a59ec57122d09a98bce12cdb5d9dc5ede336e5015f13fdc6e6ee942d456f
Tx public key: 4cf774be522441b01edee548011bcaf6c33b70c1045882a7c16f6e3f12c9591a
Timestamp: 1579050520 Timestamp [UCT]: 2020-01-15 01:08:40 Age [y:d:h:m:s]: 05:026:18:10:23
Block: 45702 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1169292 RingCT/type: yes/0
Extra: 014cf774be522441b01edee548011bcaf6c33b70c1045882a7c16f6e3f12c9591a021100000078b221b3d1000000000000000000

1 output(s) for total of 433.090474953000 dcy

stealth address amount amount idx
00: 9b5fb95ce9d42bcae33d3ad360f237a8473a51977dfd7e34be0a25af60744272 433.090474953000 83652 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": 45712, "vin": [ { "gen": { "height": 45702 } } ], "vout": [ { "amount": 433090474953, "target": { "key": "9b5fb95ce9d42bcae33d3ad360f237a8473a51977dfd7e34be0a25af60744272" } } ], "extra": [ 1, 76, 247, 116, 190, 82, 36, 65, 176, 30, 222, 229, 72, 1, 27, 202, 246, 195, 59, 112, 193, 4, 88, 130, 167, 193, 111, 110, 63, 18, 201, 89, 26, 2, 17, 0, 0, 0, 120, 178, 33, 179, 209, 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