Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ca281f9f0cf5a8826fe7d60b2b4a7a22fe25ec32f7ae6b98d45cafc23cdaf38

Tx prefix hash: f090711ffcb295068ad13fca1abfba5eaf87b9724b061aa31d78a6bda94962d7
Tx public key: db01e2cad5a038eff008367b21a7efe3e909aec16e2246527cabcadf3dc676f4
Timestamp: 1710678532 Timestamp [UCT]: 2024-03-17 12:28:52 Age [y:d:h:m:s]: 01:094:12:26:11
Block: 980292 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328424 RingCT/type: yes/0
Extra: 01db01e2cad5a038eff008367b21a7efe3e909aec16e2246527cabcadf3dc676f40211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1bf58fb63fcc6b0e344399cfc7298b60d90fd7a222b1560fa26040895452293a 0.600000000000 1440357 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": 980302, "vin": [ { "gen": { "height": 980292 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1bf58fb63fcc6b0e344399cfc7298b60d90fd7a222b1560fa26040895452293a" } } ], "extra": [ 1, 219, 1, 226, 202, 213, 160, 56, 239, 240, 8, 54, 123, 33, 167, 239, 227, 233, 9, 174, 193, 110, 34, 70, 82, 124, 171, 202, 223, 61, 198, 118, 244, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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