Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 770fcc2275b7b1858d7344ab05b9ab2e3cb3f6c8ccf52afae25919b30b8acb18

Tx prefix hash: c5fe6736419dd9f251f6d873ee75818feaf9d69412ec77ef26d208da28ec2882
Tx public key: cff0f09f0ddda7cdc3f9c22028adc99224566ae7620b5e5f0d1cd859a8c81655
Timestamp: 1635314518 Timestamp [UCT]: 2021-10-27 06:01:58 Age [y:d:h:m:s]: 03:063:04:17:59
Block: 361368 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 823580 RingCT/type: yes/0
Extra: 01cff0f09f0ddda7cdc3f9c22028adc99224566ae7620b5e5f0d1cd859a8c816550211000000331154028c000000000000000000

1 output(s) for total of 38.961728163000 dcy

stealth address amount amount idx
00: 4d4e2d9ba4e96b5383a5658f53335e4a628526472b34ce546af053e59ee0f30e 38.961728163000 735222 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": 361378, "vin": [ { "gen": { "height": 361368 } } ], "vout": [ { "amount": 38961728163, "target": { "key": "4d4e2d9ba4e96b5383a5658f53335e4a628526472b34ce546af053e59ee0f30e" } } ], "extra": [ 1, 207, 240, 240, 159, 13, 221, 167, 205, 195, 249, 194, 32, 40, 173, 201, 146, 36, 86, 106, 231, 98, 11, 94, 95, 13, 28, 216, 89, 168, 200, 22, 85, 2, 17, 0, 0, 0, 51, 17, 84, 2, 140, 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