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: 22016712a18fd68673ae2fc68bd0b18acc5d82eec6552d17accd0858c83d26a8
Tx prefix hash: c1d71fe2f38b52fdc4df02a38baed8ff850125c1e8f91ed64755b58b95cf8e55
Tx public key: f4ab11e99d2eb5f56f7af3a9673235e7afb17e5068a47678b7605e935f074646
| Timestamp: 1779896854 | Timestamp [UTC]: 2026-05-27 15:47:34 | Age [y:d:h:m:s]: 00:012:09:48:23 |
| Block: 3111 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4775 | RingCT/type: yes/0 |
| Extra: 01f4ab11e99d2eb5f56f7af3a9673235e7afb17e5068a47678b7605e935f07464602090000000426697be300 | ||
1 output(s) for total of 34.976281116287 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8e765f31ba8d66de30fadacb3c0ebe4e201b8e9708b1840cf33670dbbee48c70 | 34.976281116287 | 3711 of 0 | <fe> |
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": 3171,
"vin": [ {
"gen": {
"height": 3111
}
}
],
"vout": [ {
"amount": 34976281116287,
"target": {
"tagged_key": {
"key": "8e765f31ba8d66de30fadacb3c0ebe4e201b8e9708b1840cf33670dbbee48c70",
"view_tag": "fe"
}
}
}
],
"extra": [ 1, 244, 171, 17, 233, 157, 46, 181, 245, 111, 122, 243, 169, 103, 50, 53, 231, 175, 177, 126, 80, 104, 164, 118, 120, 183, 96, 94, 147, 95, 7, 70, 70, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}