Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bd4d0de693ec899b6da176a5fc8cf2ac2baa5e8f15a39e3ecb6cfc87bb47451

Tx prefix hash: d8632eb54b65a06270f144dd5e62535ce5f9a196cdc56cd555451e2c06d9003e
Tx public key: e950199d4fde51bce34d0a6e2358b193f6727eb99d35754a10303dd80c0368ab
Timestamp: 1677226164 Timestamp [UCT]: 2023-02-24 08:09:24 Age [y:d:h:m:s]: 02:054:20:54:30
Block: 703818 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 560813 RingCT/type: yes/0
Extra: 01e950199d4fde51bce34d0a6e2358b193f6727eb99d35754a10303dd80c0368ab02110000000374b6d784000000000000000000

1 output(s) for total of 2.857318841000 dcy

stealth address amount amount idx
00: fff4182c68215dc762d990abf5b0f57077d1d0f179601bb31c575d2f3fe7e1ad 2.857318841000 1147423 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": 703828, "vin": [ { "gen": { "height": 703818 } } ], "vout": [ { "amount": 2857318841, "target": { "key": "fff4182c68215dc762d990abf5b0f57077d1d0f179601bb31c575d2f3fe7e1ad" } } ], "extra": [ 1, 233, 80, 25, 157, 79, 222, 81, 188, 227, 77, 10, 110, 35, 88, 177, 147, 246, 114, 126, 185, 157, 53, 117, 74, 16, 48, 61, 216, 12, 3, 104, 171, 2, 17, 0, 0, 0, 3, 116, 182, 215, 132, 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