Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed3e25defd8662eee5a9430a4910c92dc1cf07d1b6f45b9c5cf7765191347bde

Tx prefix hash: f43ace7c4d8eecd0ad1b5899117d96ab1adaee322733586aa7c4e253dafc94b9
Tx public key: ffcd9a63b648ab4c9bd5f270b3e590e23bf340a22d81b17963fbff4295f1be6e
Timestamp: 1707460443 Timestamp [UCT]: 2024-02-09 06:34:03 Age [y:d:h:m:s]: 00:317:17:09:52
Block: 953589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227499 RingCT/type: yes/0
Extra: 01ffcd9a63b648ab4c9bd5f270b3e590e23bf340a22d81b17963fbff4295f1be6e0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc86282946ba62c0fb07af71e8d1031ecf22f7d3c50da313ff61507c9201ede1 0.600000000000 1412821 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": 953599, "vin": [ { "gen": { "height": 953589 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc86282946ba62c0fb07af71e8d1031ecf22f7d3c50da313ff61507c9201ede1" } } ], "extra": [ 1, 255, 205, 154, 99, 182, 72, 171, 76, 155, 213, 242, 112, 179, 229, 144, 226, 59, 243, 64, 162, 45, 129, 177, 121, 99, 251, 255, 66, 149, 241, 190, 110, 2, 17, 0, 0, 0, 4, 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