Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14aa1a5fbae92b8ea676e783203256a4291d656b3ff0cd8a4c77ba078fb2eb35

Tx prefix hash: 6c424460c3c65741c3ae8a49f46649dc09c4795ea58ce1f7112ad6bdd7e93189
Tx public key: 327c7d7067ecf860106441b831b889f57364a0f3ea1e2c10894c56e972648077
Timestamp: 1703416077 Timestamp [UCT]: 2023-12-24 11:07:57 Age [y:d:h:m:s]: 01:084:19:24:22
Block: 920069 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321723 RingCT/type: yes/0
Extra: 01327c7d7067ecf860106441b831b889f57364a0f3ea1e2c10894c56e9726480770211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2522161b1994c2b67cba5a023d802dcbc60edae8e60dd89b1444d0973a7977d3 0.600000000000 1377747 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": 920079, "vin": [ { "gen": { "height": 920069 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2522161b1994c2b67cba5a023d802dcbc60edae8e60dd89b1444d0973a7977d3" } } ], "extra": [ 1, 50, 124, 125, 112, 103, 236, 248, 96, 16, 100, 65, 184, 49, 184, 137, 245, 115, 100, 160, 243, 234, 30, 44, 16, 137, 76, 86, 233, 114, 100, 128, 119, 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