Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7858a494ca5e810b32ebb0e741db07dbc323d06f2ac4bf5744bd6ffd3617eab4

Tx prefix hash: 54e72a44b6c29dc5939de6a65e3beb4dea01f72827ac03455df51abf561bd5eb
Tx public key: b5696d66c1dd6d3437f81875896a6f6072abff4d25821616afedeb81c90333da
Timestamp: 1738588636 Timestamp [UCT]: 2025-02-03 13:17:16 Age [y:d:h:m:s]: 00:291:02:38:00
Block: 1211221 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205822 RingCT/type: yes/0
Extra: 01b5696d66c1dd6d3437f81875896a6f6072abff4d25821616afedeb81c90333da02110000000d1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c769bc529ae89a8ca7e612f43eea4d5b4fc625e1ff59145cb6c3bacf1341da0 0.600000000000 1697980 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": 1211231, "vin": [ { "gen": { "height": 1211221 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c769bc529ae89a8ca7e612f43eea4d5b4fc625e1ff59145cb6c3bacf1341da0" } } ], "extra": [ 1, 181, 105, 109, 102, 193, 221, 109, 52, 55, 248, 24, 117, 137, 106, 111, 96, 114, 171, 255, 77, 37, 130, 22, 22, 175, 237, 235, 129, 201, 3, 51, 218, 2, 17, 0, 0, 0, 13, 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