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: d3b2add42de7ec404e4a6d8a214141ceb97e1d9091320891b02fad2a316aea78
Tx prefix hash: 920880e1245d5543ff170d8e48bdfdb5615b846b098b32b3f5e17942fe135719
Tx public key: 09ce2328710ef5202a616f49bf0c4dad6fa7229191f809515af771484ee4b6af
| Timestamp: 1779643697 | Timestamp [UTC]: 2026-05-24 17:28:17 | Age [y:d:h:m:s]: 00:015:09:12:19 |
| Block: 1418 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6479 | RingCT/type: yes/0 |
| Extra: 0109ce2328710ef5202a616f49bf0c4dad6fa7229191f809515af771484ee4b6af020900000001ba6d17be00 | ||
1 output(s) for total of 35.089407127417 HMNY
| stealth address | amount | amount idx | tag |
| 00: 594e8fe4fba53d4547e5a17c4e2eca9d490215fef35767cc80e7268ade71b825 | 35.089407127417 | 1570 of 0 | <83> |
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": 1478,
"vin": [ {
"gen": {
"height": 1418
}
}
],
"vout": [ {
"amount": 35089407127417,
"target": {
"tagged_key": {
"key": "594e8fe4fba53d4547e5a17c4e2eca9d490215fef35767cc80e7268ade71b825",
"view_tag": "83"
}
}
}
],
"extra": [ 1, 9, 206, 35, 40, 113, 14, 245, 32, 42, 97, 111, 73, 191, 12, 77, 173, 111, 167, 34, 145, 145, 248, 9, 81, 90, 247, 113, 72, 78, 228, 182, 175, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}