Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c27f572b5615395ba1354c3c014743aea8727ce2c8e62113436e96fcbf5aa70c

Tx prefix hash: 44d00ee1cef32a311743c7c1d3f795ae165cc41b3e527a7edce54d007cb108ce
Tx public key: 70867c88b49ada7a381b20c7f1de571496660a41a1d6e6b09636ccfa00b95686
Timestamp: 1696851465 Timestamp [UCT]: 2023-10-09 11:37:45 Age [y:d:h:m:s]: 01:094:20:10:10
Block: 865845 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329041 RingCT/type: yes/0
Extra: 0170867c88b49ada7a381b20c7f1de571496660a41a1d6e6b09636ccfa00b95686021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.830034452000 dcy

stealth address amount amount idx
00: 6f493d325d745fb8c792f622603f53c48ab59a37df218c3a3e14d601a7b27352 0.830034452000 1320401 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": 865855, "vin": [ { "gen": { "height": 865845 } } ], "vout": [ { "amount": 830034452, "target": { "key": "6f493d325d745fb8c792f622603f53c48ab59a37df218c3a3e14d601a7b27352" } } ], "extra": [ 1, 112, 134, 124, 136, 180, 154, 218, 122, 56, 27, 32, 199, 241, 222, 87, 20, 150, 102, 10, 65, 161, 214, 230, 176, 150, 54, 204, 250, 0, 185, 86, 134, 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