Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9cfe004a93854b9a4b940e77682d60f382ab4419dbb5db0534feac5c0169ab6e

Tx prefix hash: 917752760c43c26897292d25a14fb201dce143e03ea2aad349f8b153eaa72ce8
Tx public key: 9a27258453eea53bc7b23d8a77c1bdf8900d751c964f61f3942c98bf0ea7062a
Timestamp: 1732342628 Timestamp [UCT]: 2024-11-23 06:17:08 Age [y:d:h:m:s]: 00:000:15:32:48
Block: 1159785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 459 RingCT/type: yes/0
Extra: 019a27258453eea53bc7b23d8a77c1bdf8900d751c964f61f3942c98bf0ea7062a021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69c1420ba317a28271927be1e13d530e3cd9c18771d6b07e1eb42b6ed2c06823 0.600000000000 1645424 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": 1159795, "vin": [ { "gen": { "height": 1159785 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69c1420ba317a28271927be1e13d530e3cd9c18771d6b07e1eb42b6ed2c06823" } } ], "extra": [ 1, 154, 39, 37, 132, 83, 238, 165, 59, 199, 178, 61, 138, 119, 193, 189, 248, 144, 13, 117, 28, 150, 79, 97, 243, 148, 44, 152, 191, 14, 167, 6, 42, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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