Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fffc994adc99f2f4b30699a01c9cd4a29b13dc6b779c77d1bc2676b918bf5e33

Tx prefix hash: 0be2b306cf9372837af741f61979c2582440970c3a3bbfe2a880644b6f6741d6
Tx public key: c9faa4d2ed6d3a7f6e50bf2db16363aea4632909c6d6641536d332d698e43597
Timestamp: 1736525071 Timestamp [UCT]: 2025-01-10 16:04:31 Age [y:d:h:m:s]: 00:313:09:51:51
Block: 1194411 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221518 RingCT/type: yes/0
Extra: 01c9faa4d2ed6d3a7f6e50bf2db16363aea4632909c6d6641536d332d698e4359702110000001a1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41b22b56b6aa98c2326e80201a34a6167c86cd093ed04e59d0b0fc848cb0dad8 0.600000000000 1680982 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": 1194421, "vin": [ { "gen": { "height": 1194411 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41b22b56b6aa98c2326e80201a34a6167c86cd093ed04e59d0b0fc848cb0dad8" } } ], "extra": [ 1, 201, 250, 164, 210, 237, 109, 58, 127, 110, 80, 191, 45, 177, 99, 99, 174, 164, 99, 41, 9, 198, 214, 100, 21, 54, 211, 50, 214, 152, 228, 53, 151, 2, 17, 0, 0, 0, 26, 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