Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09143678bb0edd2365d4164885018b320a90624fd7acf757adf5c3d2d9495728

Tx prefix hash: af3bc21750a4251ea78e63ee958ea1dda976103a2e885cb75ce32f0976b961e0
Tx public key: c7005f9ab427b7e951b1e786fa8f4a062fe7c43a18d1f667eb33bfb84203698f
Timestamp: 1765461155 Timestamp [UCT]: 2025-12-11 13:52:35 Age [y:d:h:m:s]: 00:028:05:48:39
Block: 1431319 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20231 RingCT/type: yes/0
Extra: 01c7005f9ab427b7e951b1e786fa8f4a062fe7c43a18d1f667eb33bfb84203698f02110000000ed6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f1ad6f23172058d964e54e6294e9e43ee579b3583d8eab3c43c75a7e674ba1c 0.600000000000 1920076 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": 1431329, "vin": [ { "gen": { "height": 1431319 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f1ad6f23172058d964e54e6294e9e43ee579b3583d8eab3c43c75a7e674ba1c" } } ], "extra": [ 1, 199, 0, 95, 154, 180, 39, 183, 233, 81, 177, 231, 134, 250, 143, 74, 6, 47, 231, 196, 58, 24, 209, 246, 103, 235, 51, 191, 184, 66, 3, 105, 143, 2, 17, 0, 0, 0, 14, 214, 225, 157, 124, 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