Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb500281ef39c25229e6c858f1560e7df59b9b930fa8a54ef7343b11bb5a92e0

Tx prefix hash: 15d7cc5b099a0f6e21c97a9ba40d0f0d49ca5161feafe535a609b05b02620a74
Tx public key: fa8297c192fd68b9986eb333223b67a8b8e10ca305f9e65196645372ed9af061
Timestamp: 1729935921 Timestamp [UCT]: 2024-10-26 09:45:21 Age [y:d:h:m:s]: 00:161:22:44:24
Block: 1139906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115532 RingCT/type: yes/0
Extra: 01fa8297c192fd68b9986eb333223b67a8b8e10ca305f9e65196645372ed9af0610211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: afaf3e27794746de4e0ee8e7d7bcd612f77a2dad789b3e00d7e409488d31d79e 0.600000000000 1623693 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": 1139916, "vin": [ { "gen": { "height": 1139906 } } ], "vout": [ { "amount": 600000000, "target": { "key": "afaf3e27794746de4e0ee8e7d7bcd612f77a2dad789b3e00d7e409488d31d79e" } } ], "extra": [ 1, 250, 130, 151, 193, 146, 253, 104, 185, 152, 110, 179, 51, 34, 59, 103, 168, 184, 225, 12, 163, 5, 249, 230, 81, 150, 100, 83, 114, 237, 154, 240, 97, 2, 17, 0, 0, 0, 4, 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