Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1be42f79862ab8d50b37f8edf7a2cdf15e9bff42b701829870ae696897ceb90e

Tx prefix hash: 89485fa5957b04da45325127919e54073c9c3021bfbb404d9b6398b1186b7737
Tx public key: 0f98cbfd27ea33fb91a4052f42d3f4a5af60616c6caa1502586ef2e774f2279b
Timestamp: 1710821163 Timestamp [UCT]: 2024-03-19 04:06:03 Age [y:d:h:m:s]: 01:066:07:00:55
Block: 981476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308379 RingCT/type: yes/0
Extra: 010f98cbfd27ea33fb91a4052f42d3f4a5af60616c6caa1502586ef2e774f2279b02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d732f5fb26e62a28a4f3e194fe71749524371217b4f65748f631c1ac02e5eb26 0.600000000000 1441573 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": 981486, "vin": [ { "gen": { "height": 981476 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d732f5fb26e62a28a4f3e194fe71749524371217b4f65748f631c1ac02e5eb26" } } ], "extra": [ 1, 15, 152, 203, 253, 39, 234, 51, 251, 145, 164, 5, 47, 66, 211, 244, 165, 175, 96, 97, 108, 108, 170, 21, 2, 88, 110, 242, 231, 116, 242, 39, 155, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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