Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08f1e14d8fe3082fca883cc611222cb48c179ba25146510853a6e8b4c681d0b9

Tx prefix hash: a85ea7f631821c08dc53d43dda6bcf7b5a53388c0ad2c1dfd65952287ce6423a
Tx public key: 1aabe528ef1103d95d62113323bcfae581981306ac32de47d3d3f4dc142c8b5a
Timestamp: 1764074964 Timestamp [UCT]: 2025-11-25 12:49:24 Age [y:d:h:m:s]: 00:069:01:23:29
Block: 1419825 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49281 RingCT/type: yes/0
Extra: 011aabe528ef1103d95d62113323bcfae581981306ac32de47d3d3f4dc142c8b5a02110000000270609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe6f72e1ffa4d9b0d494326dcb4442f6bf9c17bf6eb5b0d41fa508311045a69a 0.600000000000 1908366 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": 1419835, "vin": [ { "gen": { "height": 1419825 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe6f72e1ffa4d9b0d494326dcb4442f6bf9c17bf6eb5b0d41fa508311045a69a" } } ], "extra": [ 1, 26, 171, 229, 40, 239, 17, 3, 217, 93, 98, 17, 51, 35, 188, 250, 229, 129, 152, 19, 6, 172, 50, 222, 71, 211, 211, 244, 220, 20, 44, 139, 90, 2, 17, 0, 0, 0, 2, 112, 96, 157, 3, 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