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: 066d14b04373fc4b11a849edbad5f64c2505810adcc1fa58f4bd882166d79bdf
Tx prefix hash: 0c61e5413efbdbce473946834b66967afb07c6fdb66a697301d68d21a05446a2
Tx public key: e7806b212b0494b76b28f845a5e45324922c327b1dd73e5eb4171b3ce04cba9b
| Timestamp: 1779849742 | Timestamp [UTC]: 2026-05-27 02:42:22 | Age [y:d:h:m:s]: 00:013:00:07:26 |
| Block: 2514 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5385 | RingCT/type: yes/0 |
| Extra: 01e7806b212b0494b76b28f845a5e45324922c327b1dd73e5eb4171b3ce04cba9b02090000000426697be300 | ||
1 output(s) for total of 35.016130879486 HMNY
| stealth address | amount | amount idx | tag |
| 00: d5aebc0983fc88cdb6beedd9da0bd999dbe9d093cdd2056e70e4ce22402e7abb | 35.016130879486 | 2958 of 0 | <01> |
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": 2574,
"vin": [ {
"gen": {
"height": 2514
}
}
],
"vout": [ {
"amount": 35016130879486,
"target": {
"tagged_key": {
"key": "d5aebc0983fc88cdb6beedd9da0bd999dbe9d093cdd2056e70e4ce22402e7abb",
"view_tag": "01"
}
}
}
],
"extra": [ 1, 231, 128, 107, 33, 43, 4, 148, 183, 107, 40, 248, 69, 165, 228, 83, 36, 146, 44, 50, 123, 29, 215, 62, 94, 180, 23, 27, 60, 224, 76, 186, 155, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}