Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ca9c18bef7caa11ef68245361e59959dc5d4b8d617746b3f983bd67d1dff556

Tx prefix hash: d10d73d3336e98b8ad8740da6d3508d9190381a776c0ef44c5b0890d5d414eea
Tx public key: 951fe08810d1ae1ce66570ece5989fc9b53dd4ba8802414ae938139f75c3a412
Timestamp: 1671444767 Timestamp [UCT]: 2022-12-19 10:12:47 Age [y:d:h:m:s]: 02:111:10:02:54
Block: 655898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 601308 RingCT/type: yes/0
Extra: 01951fe08810d1ae1ce66570ece5989fc9b53dd4ba8802414ae938139f75c3a41202110000000875e3f0e9000000000000000000

1 output(s) for total of 4.118486319000 dcy

stealth address amount amount idx
00: 83ef6af6c27257653231bfb3d3cba349cfaf7809a00d93814b3a0ba221ed16d1 4.118486319000 1096477 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": 655908, "vin": [ { "gen": { "height": 655898 } } ], "vout": [ { "amount": 4118486319, "target": { "key": "83ef6af6c27257653231bfb3d3cba349cfaf7809a00d93814b3a0ba221ed16d1" } } ], "extra": [ 1, 149, 31, 224, 136, 16, 209, 174, 28, 230, 101, 112, 236, 229, 152, 159, 201, 181, 61, 212, 186, 136, 2, 65, 74, 233, 56, 19, 159, 117, 195, 164, 18, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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