Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c8759bdd305f7660ce8266ad58e2465ab70a84ce49ff89a112e9c8ec9b0d42a

Tx prefix hash: 406b2b9c863df5011b533dfd91089effae0f7c0a55510e9f6e7c5efccc39e6e1
Tx public key: 2b44f27768479a4ea9662d74435cc753becfc9db24b28ae044da2eee77fe9603
Timestamp: 1712583294 Timestamp [UCT]: 2024-04-08 13:34:54 Age [y:d:h:m:s]: 01:009:11:59:14
Block: 996041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267765 RingCT/type: yes/0
Extra: 012b44f27768479a4ea9662d74435cc753becfc9db24b28ae044da2eee77fe960302110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f03f445912b60be181a4e0da22a46d1cd0e0247d51062e02d4e8c9871d680a76 0.600000000000 1456457 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": 996051, "vin": [ { "gen": { "height": 996041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f03f445912b60be181a4e0da22a46d1cd0e0247d51062e02d4e8c9871d680a76" } } ], "extra": [ 1, 43, 68, 242, 119, 104, 71, 154, 78, 169, 102, 45, 116, 67, 92, 199, 83, 190, 207, 201, 219, 36, 178, 138, 224, 68, 218, 46, 238, 119, 254, 150, 3, 2, 17, 0, 0, 0, 1, 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