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: bf2b9ae57a6fffc258c6a5186e8e3aa4671b241c57cd029d6c135df37bf28506
Tx prefix hash: 5e0bbcffd74c84053bd53b91416018f9bcb2fb61cf22a6779ed1b45e4d0be617
Tx public key: 2825192204aa2121d7b8fd47181086245895b5bb703897b9cedaec0c59b3e671
| Timestamp: 1780004209 | Timestamp [UTC]: 2026-05-28 21:36:49 | Age [y:d:h:m:s]: 00:011:05:03:47 |
| Block: 4069 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3827 | RingCT/type: yes/0 |
| Extra: 012825192204aa2121d7b8fd47181086245895b5bb703897b9cedaec0c59b3e67102090000000d26697be300 | ||
1 output(s) for total of 34.912429349844 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5c5ef8a0a2f3f7aaa9a954c803decaa524f850ad8c7838bb73d5950a8e37785c | 34.912429349844 | 5049 of 0 | <33> |
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": 4129,
"vin": [ {
"gen": {
"height": 4069
}
}
],
"vout": [ {
"amount": 34912429349844,
"target": {
"tagged_key": {
"key": "5c5ef8a0a2f3f7aaa9a954c803decaa524f850ad8c7838bb73d5950a8e37785c",
"view_tag": "33"
}
}
}
],
"extra": [ 1, 40, 37, 25, 34, 4, 170, 33, 33, 215, 184, 253, 71, 24, 16, 134, 36, 88, 149, 181, 187, 112, 56, 151, 185, 206, 218, 236, 12, 89, 179, 230, 113, 2, 9, 0, 0, 0, 13, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}