Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92a55b77081f477c892ecc1167f8b645e0ac4774bf33ac66df11140d707b0d66

Tx prefix hash: edb706b44b4b52751f5917e538318b1e6013e8ea8e274dfd3bfee6235adb97cb
Tx public key: 26ca7febc5f72cc731e0cc94ad96d20f6d9038112046237f25ebfdaef8276186
Timestamp: 1638445223 Timestamp [UCT]: 2021-12-02 11:40:23 Age [y:d:h:m:s]: 03:035:04:59:19
Block: 386778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 804095 RingCT/type: yes/0
Extra: 0126ca7febc5f72cc731e0cc94ad96d20f6d9038112046237f25ebfdaef827618602110000000cb494d89c000000000000000000

1 output(s) for total of 32.095511224000 dcy

stealth address amount amount idx
00: 7aff4327a032c2059fd17be2e9b44d97d1a171725f0a2ad634f14afe3aa925b2 32.095511224000 780237 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": 386788, "vin": [ { "gen": { "height": 386778 } } ], "vout": [ { "amount": 32095511224, "target": { "key": "7aff4327a032c2059fd17be2e9b44d97d1a171725f0a2ad634f14afe3aa925b2" } } ], "extra": [ 1, 38, 202, 127, 235, 197, 247, 44, 199, 49, 224, 204, 148, 173, 150, 210, 15, 109, 144, 56, 17, 32, 70, 35, 127, 37, 235, 253, 174, 248, 39, 97, 134, 2, 17, 0, 0, 0, 12, 180, 148, 216, 156, 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