Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ca6479c6f28949ec9fb1ec0d35b5a9dc9b49375f1a2031c40e7b8f8c4c60944

Tx prefix hash: 8942d5fb62ebae01bff53b7a8355e1c5a922961319b6b0f8fbd8e7e8669ff17e
Tx public key: 558d76321de324a2547a1ea763dbc039a3c26d959593efffa0ae3e8fb93fd4eb
Timestamp: 1738267508 Timestamp [UCT]: 2025-01-30 20:05:08 Age [y:d:h:m:s]: 00:251:01:49:04
Block: 1208583 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177139 RingCT/type: yes/0
Extra: 01558d76321de324a2547a1ea763dbc039a3c26d959593efffa0ae3e8fb93fd4eb021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ba53afe8c652eef53ea000d6133fb2773160aefbcd5208916cf5e87a3533d20 0.600000000000 1695316 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": 1208593, "vin": [ { "gen": { "height": 1208583 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ba53afe8c652eef53ea000d6133fb2773160aefbcd5208916cf5e87a3533d20" } } ], "extra": [ 1, 85, 141, 118, 50, 29, 227, 36, 162, 84, 122, 30, 167, 99, 219, 192, 57, 163, 194, 109, 149, 149, 147, 239, 255, 160, 174, 62, 143, 185, 63, 212, 235, 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