Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3b5686710ace2f6d47522ed56efca0d3eed1585b8a123663fa708172c11f11b

Tx prefix hash: 72fde2ae2ca5f92f04fb6f65e6d73e71e18fede2414ec9e20d5312a98d3060ac
Tx public key: 8d9ba7135a5242e6f5d9f4343532b29a34719f56c36fc9bc0be09fefad98d809
Timestamp: 1751090798 Timestamp [UCT]: 2025-06-28 06:06:38 Age [y:d:h:m:s]: 00:145:16:21:21
Block: 1314322 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102208 RingCT/type: yes/0
Extra: 018d9ba7135a5242e6f5d9f4343532b29a34719f56c36fc9bc0be09fefad98d80902110000000243846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cae7e7e6886f9902e24fe8e9a949e7f29f4b1c3dd06d325df15bffe448254ccc 0.600000000000 1801969 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": 1314332, "vin": [ { "gen": { "height": 1314322 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cae7e7e6886f9902e24fe8e9a949e7f29f4b1c3dd06d325df15bffe448254ccc" } } ], "extra": [ 1, 141, 155, 167, 19, 90, 82, 66, 230, 245, 217, 244, 52, 53, 50, 178, 154, 52, 113, 159, 86, 195, 111, 201, 188, 11, 224, 159, 239, 173, 152, 216, 9, 2, 17, 0, 0, 0, 2, 67, 132, 109, 102, 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