Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35732e8be88ab84eb8c5eec35a7bd405362ec3e34695738465e337d9304bc9c8

Tx prefix hash: b5c1b17f09141be58ea4801568ce59eee820111dcf409d04e9440f2eca1a7cb4
Tx public key: c673e9f06158fb26c8e193a4d1816a909ab0a8f7ab890ca190aacee1ca83b957
Timestamp: 1750288728 Timestamp [UCT]: 2025-06-18 23:18:48 Age [y:d:h:m:s]: 00:150:03:09:22
Block: 1307967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105112 RingCT/type: yes/0
Extra: 01c673e9f06158fb26c8e193a4d1816a909ab0a8f7ab890ca190aacee1ca83b95702110000000343846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f02b50ad7ea4fbf72c2c74a030bf18b43f7a65daaacdc0598e62c0fc984a35b8 0.600000000000 1795578 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": 1307977, "vin": [ { "gen": { "height": 1307967 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f02b50ad7ea4fbf72c2c74a030bf18b43f7a65daaacdc0598e62c0fc984a35b8" } } ], "extra": [ 1, 198, 115, 233, 240, 97, 88, 251, 38, 200, 225, 147, 164, 209, 129, 106, 144, 154, 176, 168, 247, 171, 137, 12, 161, 144, 170, 206, 225, 202, 131, 185, 87, 2, 17, 0, 0, 0, 3, 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