Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9527cb851dfe1caa8a2c9760217f4f984fb18b5a96c078b3ccb5b5359c34d5ef

Tx prefix hash: 86a7152ead16bbeb4a59a9ce9c0910097b4023061f0389872518157039c5ba69
Tx public key: cd42a1084b70165ac7cd903bc40dbc7c871fe590d602086cd8f05c671a7f4664
Timestamp: 1722784668 Timestamp [UCT]: 2024-08-04 15:17:48 Age [y:d:h:m:s]: 01:065:05:39:24
Block: 1080638 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305055 RingCT/type: yes/0
Extra: 01cd42a1084b70165ac7cd903bc40dbc7c871fe590d602086cd8f05c671a7f466402110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca56752b9387d60314e676705b6ea3baf34c2afe8d8d37d5443f4a9b6606a5f2 0.600000000000 1554077 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": 1080648, "vin": [ { "gen": { "height": 1080638 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca56752b9387d60314e676705b6ea3baf34c2afe8d8d37d5443f4a9b6606a5f2" } } ], "extra": [ 1, 205, 66, 161, 8, 75, 112, 22, 90, 199, 205, 144, 59, 196, 13, 188, 124, 135, 31, 229, 144, 214, 2, 8, 108, 216, 240, 92, 103, 26, 127, 70, 100, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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