Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0dc73240fcdc6b5ec14573c415e8d8a09dd8981a593c08a63960e9042b64ba08

Tx prefix hash: fcf79dec27fb53796f0e91868a18036337f1d9f9a237f00a2eefd8bf38e63cdc
Tx public key: 0595f4e9c00afa701c20c85d34567778b02f0db56692c1af500f4940d2b57827
Timestamp: 1723089784 Timestamp [UCT]: 2024-08-08 04:03:04 Age [y:d:h:m:s]: 00:171:18:54:58
Block: 1083170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122741 RingCT/type: yes/0
Extra: 010595f4e9c00afa701c20c85d34567778b02f0db56692c1af500f4940d2b57827021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 830cdffc0baddd9f40773f517d7fdf74d23e94a5a4570d3d08bbffb0b0c7a616 0.600000000000 1557005 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": 1083180, "vin": [ { "gen": { "height": 1083170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "830cdffc0baddd9f40773f517d7fdf74d23e94a5a4570d3d08bbffb0b0c7a616" } } ], "extra": [ 1, 5, 149, 244, 233, 192, 10, 250, 112, 28, 32, 200, 93, 52, 86, 119, 120, 176, 47, 13, 181, 102, 146, 193, 175, 80, 15, 73, 64, 210, 181, 120, 39, 2, 17, 0, 0, 0, 6, 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