Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cba22d738a7d9ab5c7456499536f656f12bd5265a63d1b4c39ebc4c258b17ddb

Tx prefix hash: 69d09ae21a45481b8ab35e0c6054d63e4e5ee104ebdfdd58845ad8b12b4bef38
Tx public key: 59b4f84acdef79d621e9d069577a833988140f2bb3f122646600d39f30c9bf17
Timestamp: 1680091064 Timestamp [UCT]: 2023-03-29 11:57:44 Age [y:d:h:m:s]: 02:060:06:48:53
Block: 727589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 564636 RingCT/type: yes/0
Extra: 0159b4f84acdef79d621e9d069577a833988140f2bb3f122646600d39f30c9bf170211000000015029cbac000000000000000000

1 output(s) for total of 2.383394004000 dcy

stealth address amount amount idx
00: 3632610ea6e841e475b6b9cb72292f14eaa9364906e81b90f70f77083f983e6d 2.383394004000 1172904 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": 727599, "vin": [ { "gen": { "height": 727589 } } ], "vout": [ { "amount": 2383394004, "target": { "key": "3632610ea6e841e475b6b9cb72292f14eaa9364906e81b90f70f77083f983e6d" } } ], "extra": [ 1, 89, 180, 248, 74, 205, 239, 121, 214, 33, 233, 208, 105, 87, 122, 131, 57, 136, 20, 15, 43, 179, 241, 34, 100, 102, 0, 211, 159, 48, 201, 191, 23, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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