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: 5909b86275f0094fca70a136f42587238dc03a48ad4b3cdbf0ecf9b96a8655d6
Tx prefix hash: ca3394880a9fb3413c1d7fc30fce907aa9c36c3ffe1e2c859713a4fc7463c9e6
Tx public key: 7bcffb98717a7673df9e7c424d2564b608d4e91e1c37d35c08a65620ab97ca4e
| Timestamp: 1779699295 | Timestamp [UTC]: 2026-05-25 08:54:55 | Age [y:d:h:m:s]: 00:014:18:43:55 |
| Block: 1546 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0820 kB |
| Tx version: 2 | No of confirmations: 6403 | RingCT/type: yes/0 |
| Extra: 017bcffb98717a7673df9e7c424d2564b608d4e91e1c37d35c08a65620ab97ca4e | ||
1 output(s) for total of 35.080841415123 HMNY
| stealth address | amount | amount idx | tag |
| 00: bed0ec835effc1afacd93a376cccb1ec9770e3442d430ddb78543091a70061ad | 35.080841415123 | 1704 of 0 | <87> |
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": 1606,
"vin": [ {
"gen": {
"height": 1546
}
}
],
"vout": [ {
"amount": 35080841415123,
"target": {
"tagged_key": {
"key": "bed0ec835effc1afacd93a376cccb1ec9770e3442d430ddb78543091a70061ad",
"view_tag": "87"
}
}
}
],
"extra": [ 1, 123, 207, 251, 152, 113, 122, 118, 115, 223, 158, 124, 66, 77, 37, 100, 182, 8, 212, 233, 30, 28, 55, 211, 92, 8, 166, 86, 32, 171, 151, 202, 78
],
"rct_signatures": {
"type": 0
}
}