Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4bde9ae5e87e31f289c7d8fa17647145b9b4e14a5b9de984322bb9c3bb39b1a

Tx prefix hash: bf16d76cda32baa8c121aeebd267e9a589bd00f1fa30c025d16199668418c26d
Tx public key: 87d3d3cf17d51f4ab23596a7d4d0ff8b0212581285d930583f41bc1ad800cf1b
Timestamp: 1750763618 Timestamp [UCT]: 2025-06-24 11:13:38 Age [y:d:h:m:s]: 00:150:00:43:26
Block: 1311780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105153 RingCT/type: yes/0
Extra: 0187d3d3cf17d51f4ab23596a7d4d0ff8b0212581285d930583f41bc1ad800cf1b02110000000abf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bcb4ec77f09f3ad6c0bdef41bab471acbddbc9af853423fdd0b49e36d5e72976 0.600000000000 1799409 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": 1311790, "vin": [ { "gen": { "height": 1311780 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcb4ec77f09f3ad6c0bdef41bab471acbddbc9af853423fdd0b49e36d5e72976" } } ], "extra": [ 1, 135, 211, 211, 207, 23, 213, 31, 74, 178, 53, 150, 167, 212, 208, 255, 139, 2, 18, 88, 18, 133, 217, 48, 88, 63, 65, 188, 26, 216, 0, 207, 27, 2, 17, 0, 0, 0, 10, 191, 81, 178, 162, 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