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: 0716367bc7535bbb4f5ca01a8711740568e019dda6e3f9505aa4efb0805fed68
Tx prefix hash: 449e747fbb3f2ab46df7bff0191ea3ff5d20fe5131d7d0e52059bd012a2f1f02
Tx public key: bb33cc30b32859757a5d0ef9e23c7bdf78b8bc361ec7192eacddb1c878ec465b
| Timestamp: 1779478906 | Timestamp [UTC]: 2026-05-22 19:41:46 | Age [y:d:h:m:s]: 00:017:05:05:01 |
| Block: 635 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7251 | RingCT/type: yes/0 |
| Extra: 01bb33cc30b32859757a5d0ef9e23c7bdf78b8bc361ec7192eacddb1c878ec465b02090000001393369e7d00 | ||
1 output(s) for total of 35.141850743460 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8a686d22c89f58a62e88395c4f33789aab9ca284614024b09a7c869c224455b2 | 35.141850743460 | 669 of 0 | <7a> |
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": 695,
"vin": [ {
"gen": {
"height": 635
}
}
],
"vout": [ {
"amount": 35141850743460,
"target": {
"tagged_key": {
"key": "8a686d22c89f58a62e88395c4f33789aab9ca284614024b09a7c869c224455b2",
"view_tag": "7a"
}
}
}
],
"extra": [ 1, 187, 51, 204, 48, 179, 40, 89, 117, 122, 93, 14, 249, 226, 60, 123, 223, 120, 184, 188, 54, 30, 199, 25, 46, 172, 221, 177, 200, 120, 236, 70, 91, 2, 9, 0, 0, 0, 19, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}