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: 172e98594f9924543e278a537bac81b15c05a8ad88ac0e63f087e742228ff8da
Tx prefix hash: a1076f4dc221fb8ed24a595184adc303d07bd98ba56dabf0a47e264f5e45712d
Tx public key: 63c59620157e6908237e085674e893f88af92e2122b0d761e3389bb5b0638de5
| Timestamp: 1779450514 | Timestamp [UTC]: 2026-05-22 11:48:34 | Age [y:d:h:m:s]: 00:017:11:30:19 |
| Block: 319 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7567 | RingCT/type: yes/0 |
| Extra: 0163c59620157e6908237e085674e893f88af92e2122b0d761e3389bb5b0638de50209000000024438f87f00 | ||
1 output(s) for total of 35.163037920481 HMNY
| stealth address | amount | amount idx | tag |
| 00: b6288ab2b8ed96640538a442411f2ca558e0cdab001e70b7f97e5e4bd80cf4ec | 35.163037920481 | 315 of 0 | <04> |
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": 379,
"vin": [ {
"gen": {
"height": 319
}
}
],
"vout": [ {
"amount": 35163037920481,
"target": {
"tagged_key": {
"key": "b6288ab2b8ed96640538a442411f2ca558e0cdab001e70b7f97e5e4bd80cf4ec",
"view_tag": "04"
}
}
}
],
"extra": [ 1, 99, 197, 150, 32, 21, 126, 105, 8, 35, 126, 8, 86, 116, 232, 147, 248, 138, 249, 46, 33, 34, 176, 215, 97, 227, 56, 155, 181, 176, 99, 141, 229, 2, 9, 0, 0, 0, 2, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}