Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e0c5fe5a2fa47032f46fe73355f7f682cb309fc99b0de00249a83028c953cb8

Tx prefix hash: b913835d43f54675c23ea19f4fca55b7f5bde382843986682665009d3dd9d16c
Tx public key: 9ba2cd52e5c0074ffad212e2fd11c63c98406182292c95bf0e17065a67aae02e
Timestamp: 1674731790 Timestamp [UCT]: 2023-01-26 11:16:30 Age [y:d:h:m:s]: 01:352:12:36:26
Block: 683135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 512934 RingCT/type: yes/0
Extra: 019ba2cd52e5c0074ffad212e2fd11c63c98406182292c95bf0e17065a67aae02e0211000000015029cbac000000000000000000

1 output(s) for total of 3.345723911000 dcy

stealth address amount amount idx
00: 350dfbcf14540978c5b37703a752de483a9178ac35e89b84e59777a09a36c0c3 3.345723911000 1125306 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": 683145, "vin": [ { "gen": { "height": 683135 } } ], "vout": [ { "amount": 3345723911, "target": { "key": "350dfbcf14540978c5b37703a752de483a9178ac35e89b84e59777a09a36c0c3" } } ], "extra": [ 1, 155, 162, 205, 82, 229, 192, 7, 79, 250, 210, 18, 226, 253, 17, 198, 60, 152, 64, 97, 130, 41, 44, 149, 191, 14, 23, 6, 90, 103, 170, 224, 46, 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