Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6f67e49ebbad9d6fe5a4bccdfd358322aa24f3db1c81d4947ed46300a132caf

Tx prefix hash: d3db3e7480ff43a9c3c167474772728fd259c8e5b0926f8fd71755c82a4974b0
Tx public key: c9a6686ded43b5ebf6f35ebca409f3e307f67c4d90604c1deb0dc81f9f010a0b
Timestamp: 1713123570 Timestamp [UCT]: 2024-04-14 19:39:30 Age [y:d:h:m:s]: 00:358:14:08:05
Block: 1000524 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256369 RingCT/type: yes/0
Extra: 01c9a6686ded43b5ebf6f35ebca409f3e307f67c4d90604c1deb0dc81f9f010a0b02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 642b5f65f7518f4576da0b17d91c59ef86b9863455c00c84f81ea7790f29fb4a 0.600000000000 1461022 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": 1000534, "vin": [ { "gen": { "height": 1000524 } } ], "vout": [ { "amount": 600000000, "target": { "key": "642b5f65f7518f4576da0b17d91c59ef86b9863455c00c84f81ea7790f29fb4a" } } ], "extra": [ 1, 201, 166, 104, 109, 237, 67, 181, 235, 246, 243, 94, 188, 164, 9, 243, 227, 7, 246, 124, 77, 144, 96, 76, 29, 235, 13, 200, 31, 159, 1, 10, 11, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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