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: a6a139163e11c3fe4a2fef5e977508c85f861e1689cd493b1e6396cd219481f9
Tx prefix hash: 9bf95ece6ad1a375490daeef774722589995959c7991de95d1c5535d3db2cf7a
Tx public key: 3c61d8e0d7c8679287940914f60a4d9df56a31c8ae275ba45b86d953b3451915
| Timestamp: 1780688994 | Timestamp [UTC]: 2026-06-05 19:49:54 | Age [y:d:h:m:s]: 00:003:04:56:53 |
| Block: 5561 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2325 | RingCT/type: yes/0 |
| Extra: 013c61d8e0d7c8679287940914f60a4d9df56a31c8ae275ba45b86d953b3451915020900000001e49593ff00 | ||
1 output(s) for total of 34.813217948121 HMNY
| stealth address | amount | amount idx | tag |
| 00: d7be03ecf1604cb7fbf2eec82546b7d7a3ec8f94a3a7314614d6c8f4d3ca2818 | 34.813217948121 | 7006 of 0 | <06> |
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": 5621,
"vin": [ {
"gen": {
"height": 5561
}
}
],
"vout": [ {
"amount": 34813217948121,
"target": {
"tagged_key": {
"key": "d7be03ecf1604cb7fbf2eec82546b7d7a3ec8f94a3a7314614d6c8f4d3ca2818",
"view_tag": "06"
}
}
}
],
"extra": [ 1, 60, 97, 216, 224, 215, 200, 103, 146, 135, 148, 9, 20, 246, 10, 77, 157, 245, 106, 49, 200, 174, 39, 91, 164, 91, 134, 217, 83, 179, 69, 25, 21, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}