Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56fa27f881a877d74600b5edf1efa299d4409057b94e84d1be5c4ca9ec82a547

Tx prefix hash: a7c17245cb9c8532af7bbdf45468dec70275bd9e631561833a36a615419dfb0d
Tx public key: 8c97217674ce3235b99a57fc0f1ecae7888f9af3c1d56d4f1802efab7d3f292a
Timestamp: 1713973247 Timestamp [UCT]: 2024-04-24 15:40:47 Age [y:d:h:m:s]: 01:033:03:19:08
Block: 1007590 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284640 RingCT/type: yes/0
Extra: 018c97217674ce3235b99a57fc0f1ecae7888f9af3c1d56d4f1802efab7d3f292a0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dbafbf260a6273ece5bc232b8de966c24173a6364d3c9e58ac6975a2756ba35b 0.600000000000 1468982 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": 1007600, "vin": [ { "gen": { "height": 1007590 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dbafbf260a6273ece5bc232b8de966c24173a6364d3c9e58ac6975a2756ba35b" } } ], "extra": [ 1, 140, 151, 33, 118, 116, 206, 50, 53, 185, 154, 87, 252, 15, 30, 202, 231, 136, 143, 154, 243, 193, 213, 109, 79, 24, 2, 239, 171, 125, 63, 41, 42, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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