Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1dd5f42c5317f144ea665a6215942ded8b280d3742f2f3fcdc29673d04bc8ee3

Tx prefix hash: 99765e4252fc7d936ea04d25adeb995a10239a6f80ee7783c780e7e15f95a814
Tx public key: c03e40c18cddd0b8acfb00e16245a20cd85378db97aa520b4bfd71d6ce347e84
Timestamp: 1700814616 Timestamp [UCT]: 2023-11-24 08:30:16 Age [y:d:h:m:s]: 01:144:02:42:33
Block: 898497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364174 RingCT/type: yes/0
Extra: 01c03e40c18cddd0b8acfb00e16245a20cd85378db97aa520b4bfd71d6ce347e84021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.647003218000 dcy

stealth address amount amount idx
00: 1c47f47cedacb14c34db9628227a78e8af2536de045edffe4323e839bfdf3dff 0.647003218000 1354918 of 0

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": 898507, "vin": [ { "gen": { "height": 898497 } } ], "vout": [ { "amount": 647003218, "target": { "key": "1c47f47cedacb14c34db9628227a78e8af2536de045edffe4323e839bfdf3dff" } } ], "extra": [ 1, 192, 62, 64, 193, 140, 221, 208, 184, 172, 251, 0, 225, 98, 69, 162, 12, 216, 83, 120, 219, 151, 170, 82, 11, 75, 253, 113, 214, 206, 52, 126, 132, 2, 17, 0, 0, 0, 6, 230, 210, 127, 156, 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