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: 1b6566a5d5edb0b127ee609d70b8176b51539ecbcff989f2027202552ee325e8
Tx prefix hash: ff0009de7b747e39312315eb4d4ba9fa0ef0823c99167a03f02f78973ad1cdb5
Tx public key: 0270858b7664966a41c58b34ea082ae5c8548b3fd963addc0f8e7d640468501c
| Timestamp: 1779631164 | Timestamp [UTC]: 2026-05-24 13:59:24 | Age [y:d:h:m:s]: 00:015:10:47:23 |
| Block: 898 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6988 | RingCT/type: yes/0 |
| Extra: 010270858b7664966a41c58b34ea082ae5c8548b3fd963addc0f8e7d640468501c020900000001ba6d17be00 | ||
1 output(s) for total of 35.126829646248 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8f775b535050c32da66cb47805d4923ed94b6c4b698401c838049120628dd3ca | 35.126829646248 | 1030 of 0 | <74> |
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": 958,
"vin": [ {
"gen": {
"height": 898
}
}
],
"vout": [ {
"amount": 35126829646248,
"target": {
"tagged_key": {
"key": "8f775b535050c32da66cb47805d4923ed94b6c4b698401c838049120628dd3ca",
"view_tag": "74"
}
}
}
],
"extra": [ 1, 2, 112, 133, 139, 118, 100, 150, 106, 65, 197, 139, 52, 234, 8, 42, 229, 200, 84, 139, 63, 217, 99, 173, 220, 15, 142, 125, 100, 4, 104, 80, 28, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}