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: 6912002188b720e41c5d94e03c3b20858e400a4ab372a7dcc8f250d70a9c1919
Tx prefix hash: d95e4c7daacc3a9b18ff7f1a8971411cf3aaf2c17ab1bf44f500a8ed2fc54971
Tx public key: 9443c5e2ee077bf840022bd7ea67aa32d669de1b2ce2a40692abc73a1f4f4374
| Timestamp: 1780826347 | Timestamp [UTC]: 2026-06-07 09:59:07 | Age [y:d:h:m:s]: 00:009:22:02:38 |
| Block: 7272 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1473 | RingCT/type: yes/0 |
| Extra: 019443c5e2ee077bf840022bd7ea67aa32d669de1b2ce2a40692abc73a1f4f4374020900000001e49593ff00 | ||
1 output(s) for total of 34.699791008926 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9ac86fd396c5255b85b1cb8c4312547d322c9c12cfb5b609a5c7dcf9ca495e3f | 34.699791008926 | 8952 of 0 | <79> |
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": 7332,
"vin": [ {
"gen": {
"height": 7272
}
}
],
"vout": [ {
"amount": 34699791008926,
"target": {
"tagged_key": {
"key": "9ac86fd396c5255b85b1cb8c4312547d322c9c12cfb5b609a5c7dcf9ca495e3f",
"view_tag": "79"
}
}
}
],
"extra": [ 1, 148, 67, 197, 226, 238, 7, 123, 248, 64, 2, 43, 215, 234, 103, 170, 50, 214, 105, 222, 27, 44, 226, 164, 6, 146, 171, 199, 58, 31, 79, 67, 116, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}