Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 319959439d3c0c2b057948c881c464981b716dc37d38478d14288e0a2c129a83

Tx prefix hash: 60f49bf4a63435c240f5e99747d7ceae11fac64c001b6aa31d04a36fd3f1e468
Tx public key: ae53083a50cea2c72bd34a08dcac989d51b257b489872eee76e9502c39480239
Timestamp: 1578938260 Timestamp [UCT]: 2020-01-13 17:57:40 Age [y:d:h:m:s]: 04:350:14:50:40
Block: 44852 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1140049 RingCT/type: yes/0
Extra: 01ae53083a50cea2c72bd34a08dcac989d51b257b489872eee76e9502c394802390211000000552264afe6000000000000000000

1 output(s) for total of 435.900679058000 dcy

stealth address amount amount idx
00: 0d66e01d0b87d91115a88834241c82f3589d8f5d24a44a4b8cf8846f93b2470f 435.900679058000 81751 of 0

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": 44862, "vin": [ { "gen": { "height": 44852 } } ], "vout": [ { "amount": 435900679058, "target": { "key": "0d66e01d0b87d91115a88834241c82f3589d8f5d24a44a4b8cf8846f93b2470f" } } ], "extra": [ 1, 174, 83, 8, 58, 80, 206, 162, 199, 43, 211, 74, 8, 220, 172, 152, 157, 81, 178, 87, 180, 137, 135, 46, 238, 118, 233, 80, 44, 57, 72, 2, 57, 2, 17, 0, 0, 0, 85, 34, 100, 175, 230, 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