Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 179fb371a125c6e933045ea2161c76c344b88c6ef7078af03cc8a18761396d17

Tx prefix hash: 070836c3c8b79a9df28581f135eed64c6f16271899e6afb3910bc6ddd40431cd
Tx public key: d45c0a46bcb67c50b15f252919d472b263d4a63d7c8933f96f09b6bd7efb3a94
Timestamp: 1708690271 Timestamp [UCT]: 2024-02-23 12:11:11 Age [y:d:h:m:s]: 01:030:12:20:27
Block: 963790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282817 RingCT/type: yes/0
Extra: 01d45c0a46bcb67c50b15f252919d472b263d4a63d7c8933f96f09b6bd7efb3a9402110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4385a98cca95c59b9a2f44382f1cff4e8649c11830b780934aac2fff577536ed 0.600000000000 1423517 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": 963800, "vin": [ { "gen": { "height": 963790 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4385a98cca95c59b9a2f44382f1cff4e8649c11830b780934aac2fff577536ed" } } ], "extra": [ 1, 212, 92, 10, 70, 188, 182, 124, 80, 177, 95, 37, 41, 25, 212, 114, 178, 99, 212, 166, 61, 124, 137, 51, 249, 111, 9, 182, 189, 126, 251, 58, 148, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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