Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fedd62806445482d06ea41dc60f78305fea739d4de5809e7b0ab0c45aea5d24a

Tx prefix hash: 1c7647dd78ea82215bf4dbc449df01aee1132a2e035ee4fc37c4848b3dec7ffd
Tx public key: cb055be712d8a92970384491f53cd1d2ecb35e0333a6bdc37f6b69661ec4670a
Timestamp: 1711850734 Timestamp [UCT]: 2024-03-31 02:05:34 Age [y:d:h:m:s]: 01:222:14:16:28
Block: 990011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 417753 RingCT/type: yes/0
Extra: 01cb055be712d8a92970384491f53cd1d2ecb35e0333a6bdc37f6b69661ec4670a02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f6913ef58fc5fbd2ec1b316cf0396feb8b911a9d8f14748a4d096e54b3f47d2 0.600000000000 1450329 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": 990021, "vin": [ { "gen": { "height": 990011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f6913ef58fc5fbd2ec1b316cf0396feb8b911a9d8f14748a4d096e54b3f47d2" } } ], "extra": [ 1, 203, 5, 91, 231, 18, 216, 169, 41, 112, 56, 68, 145, 245, 60, 209, 210, 236, 179, 94, 3, 51, 166, 189, 195, 127, 107, 105, 102, 30, 196, 103, 10, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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