Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9839a098c1398f5cd721e3363f6956f8bd205afbf51d0cadc0bd82a1d2df9f5a

Tx prefix hash: 245cc330489310c730529ceeaaf43dfe7f8ebcc6518c4eafd4b94741124e484a
Tx public key: 6c02135f0754f4625c4a92f2e44df631ec9db36879f236b537d9e6d1aad67aa9
Timestamp: 1735506271 Timestamp [UCT]: 2024-12-29 21:04:31 Age [y:d:h:m:s]: 00:109:11:23:18
Block: 1185976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78046 RingCT/type: yes/0
Extra: 016c02135f0754f4625c4a92f2e44df631ec9db36879f236b537d9e6d1aad67aa90211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 052c388432fcf10dbe96008f3d5588efa17e33d0180ee86f5d69cca11990821c 0.600000000000 1672451 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": 1185986, "vin": [ { "gen": { "height": 1185976 } } ], "vout": [ { "amount": 600000000, "target": { "key": "052c388432fcf10dbe96008f3d5588efa17e33d0180ee86f5d69cca11990821c" } } ], "extra": [ 1, 108, 2, 19, 95, 7, 84, 244, 98, 92, 74, 146, 242, 228, 77, 246, 49, 236, 157, 179, 104, 121, 242, 54, 181, 55, 217, 230, 209, 170, 214, 122, 169, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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