Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 567ab8913517f154bde34a8e8627d6628c9a5ce33569feb1dd9da5d3c2cf7821

Tx prefix hash: 1fc8a537ca5521763077211ee4c168e68193aed0be712e7a9affbe498de71db5
Tx public key: aecd37cdab65e3ae5facc976f70695c94ee17faec96d7f2731ff35dd6bc9a0d9
Timestamp: 1710765245 Timestamp [UCT]: 2024-03-18 12:34:05 Age [y:d:h:m:s]: 01:000:22:16:45
Block: 981010 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261645 RingCT/type: yes/0
Extra: 01aecd37cdab65e3ae5facc976f70695c94ee17faec96d7f2731ff35dd6bc9a0d902110000001759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8e705c8cc18cdf14c17f4058ecf30356c032e111e95dc0c70aa42e3d7e0c77b 0.600000000000 1441095 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": 981020, "vin": [ { "gen": { "height": 981010 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8e705c8cc18cdf14c17f4058ecf30356c032e111e95dc0c70aa42e3d7e0c77b" } } ], "extra": [ 1, 174, 205, 55, 205, 171, 101, 227, 174, 95, 172, 201, 118, 247, 6, 149, 201, 78, 225, 127, 174, 201, 109, 127, 39, 49, 255, 53, 221, 107, 201, 160, 217, 2, 17, 0, 0, 0, 23, 89, 218, 211, 245, 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