For RingCT transactions, outputs' amounts are also decoded
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Tx hash: aef1c3ad9d47c6fa8de49fd0a6eae6b7bfbaf82508e693870518ca58ba7ef7f6
Tx prefix hash: de7dfb8add2fe267bd498c1e08888c0b8ed8d62c930d7d935ae11596996899be
Tx public key: 4db56eada2ecbd98c172f4cab66f9b41840e8f8dfd789d13ab91e6b2399751cb
| Timestamp: 1780689269 | Timestamp [UTC]: 2026-06-05 19:54:29 | Age [y:d:h:m:s]: 00:003:01:17:38 |
| Block: 5580 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2306 | RingCT/type: yes/0 |
| Extra: 014db56eada2ecbd98c172f4cab66f9b41840e8f8dfd789d13ab91e6b2399751cb020900000001e49593ff00 | ||
1 output(s) for total of 34.811956351848 HMNY
| stealth address | amount | amount idx | tag |
| 00: bb614fdfb20a97e8e78728f09b50a53fc6234fccc69903179d3a61332d390e99 | 34.811956351848 | 7025 of 0 | <ba> |
Check which outputs belong to given HMNY 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 HMNY in this transaction
Tx private key can be obtained using get_tx_key
command in hashmonkey-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": 5640,
"vin": [ {
"gen": {
"height": 5580
}
}
],
"vout": [ {
"amount": 34811956351848,
"target": {
"tagged_key": {
"key": "bb614fdfb20a97e8e78728f09b50a53fc6234fccc69903179d3a61332d390e99",
"view_tag": "ba"
}
}
}
],
"extra": [ 1, 77, 181, 110, 173, 162, 236, 189, 152, 193, 114, 244, 202, 182, 111, 155, 65, 132, 14, 143, 141, 253, 120, 157, 19, 171, 145, 230, 178, 57, 151, 81, 203, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}