Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 159b0dbdad38780ae817f4345755e08bb2a5464c049543b6e053b2f6adb7d8a0

Tx prefix hash: e93d885086d3a16edbd05be4cbc2740c8f821df38f9c51ad9e80b77babb3a568
Tx public key: 07b155d623c10a9d15198055e8efabcdd8a506248b16e57aedc5445fff3f760f
Timestamp: 1736629526 Timestamp [UCT]: 2025-01-11 21:05:26 Age [y:d:h:m:s]: 00:343:06:21:25
Block: 1195272 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242905 RingCT/type: yes/0
Extra: 0107b155d623c10a9d15198055e8efabcdd8a506248b16e57aedc5445fff3f760f0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e0319db5be8ae677be1653237a9f1ff32bda86e7a115848658ac845ed4aeae6 0.600000000000 1681861 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": 1195282, "vin": [ { "gen": { "height": 1195272 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e0319db5be8ae677be1653237a9f1ff32bda86e7a115848658ac845ed4aeae6" } } ], "extra": [ 1, 7, 177, 85, 214, 35, 193, 10, 157, 21, 25, 128, 85, 232, 239, 171, 205, 216, 165, 6, 36, 139, 22, 229, 122, 237, 197, 68, 95, 255, 63, 118, 15, 2, 17, 0, 0, 0, 2, 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