Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e127afab3e72a88ba87f66749b8fac16d7aba025efad19cea9009a8001b46a2

Tx prefix hash: 23c9fbb63916f8c5276beac9b9b59ce05bf1b1e008deb1acbcfc4a5c070ec320
Tx public key: f1c9ab81eb98b4daf4a135e1989a61148782dd6a238e2b565294cede26cb16fb
Timestamp: 1694224774 Timestamp [UCT]: 2023-09-09 01:59:34 Age [y:d:h:m:s]: 01:109:00:13:05
Block: 844050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339227 RingCT/type: yes/0
Extra: 01f1c9ab81eb98b4daf4a135e1989a61148782dd6a238e2b565294cede26cb16fb021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.980193986000 dcy

stealth address amount amount idx
00: 12a01c6fab7b7111e5c7770723bff32013fb18e7cf601d799b6f723aab3e17a3 0.980193986000 1297334 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": 844060, "vin": [ { "gen": { "height": 844050 } } ], "vout": [ { "amount": 980193986, "target": { "key": "12a01c6fab7b7111e5c7770723bff32013fb18e7cf601d799b6f723aab3e17a3" } } ], "extra": [ 1, 241, 201, 171, 129, 235, 152, 180, 218, 244, 161, 53, 225, 152, 154, 97, 20, 135, 130, 221, 106, 35, 142, 43, 86, 82, 148, 206, 222, 38, 203, 22, 251, 2, 17, 0, 0, 0, 2, 230, 210, 127, 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