Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d35dbe253d49dd8ffd8839fb01f07f6f2517ef1c19ada518050d069bbca7a02

Tx prefix hash: f3b89dcf25504dcd2bbbe56462c993480375026bfd167a51e90c254b9cd47eba
Tx public key: 36c70a7b64a36770d39d401499fa3f3c4dbbc70a3bbf038046e88139f148c06c
Timestamp: 1685300376 Timestamp [UCT]: 2023-05-28 18:59:36 Age [y:d:h:m:s]: 01:230:08:47:24
Block: 770123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 426076 RingCT/type: yes/0
Extra: 0136c70a7b64a36770d39d401499fa3f3c4dbbc70a3bbf038046e88139f148c06c021100000001e6d27f9c000000000000000000

1 output(s) for total of 1.722911546000 dcy

stealth address amount amount idx
00: fd73d20759aec7ad7563cb0a24ff1b89d80567f9fbdb09c90ec66df82054ca35 1.722911546000 1219410 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": 770133, "vin": [ { "gen": { "height": 770123 } } ], "vout": [ { "amount": 1722911546, "target": { "key": "fd73d20759aec7ad7563cb0a24ff1b89d80567f9fbdb09c90ec66df82054ca35" } } ], "extra": [ 1, 54, 199, 10, 123, 100, 163, 103, 112, 211, 157, 64, 20, 153, 250, 63, 60, 77, 187, 199, 10, 59, 191, 3, 128, 70, 232, 129, 57, 241, 72, 192, 108, 2, 17, 0, 0, 0, 1, 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