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: 4db977d437378522ed7e8e8a9443246d902366c875ae65071ba11b24e8e5278f
Tx prefix hash: 5e4cdc4ffd6014d87afec4f25914c28c029b2202879dcb8ff6c618d640fdf7e7
Tx public key: ed043b3a4dd8e949844e2e519fd2777b0e87b059563994d863b9a6aaa1c8bbc5
| Timestamp: 1779452075 | Timestamp [UTC]: 2026-05-22 12:14:35 | Age [y:d:h:m:s]: 00:017:14:35:13 |
| Block: 342 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7578 | RingCT/type: yes/0 |
| Extra: 01ed043b3a4dd8e949844e2e519fd2777b0e87b059563994d863b9a6aaa1c8bbc50209000000034438f87f00 | ||
1 output(s) for total of 35.161495384882 HMNY
| stealth address | amount | amount idx | tag |
| 00: c4d47579c21cde70596660e78bf10bcf8cfbbec37277ea4f8c0227e47f4daecf | 35.161495384882 | 338 of 0 | <dd> |
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": 402,
"vin": [ {
"gen": {
"height": 342
}
}
],
"vout": [ {
"amount": 35161495384882,
"target": {
"tagged_key": {
"key": "c4d47579c21cde70596660e78bf10bcf8cfbbec37277ea4f8c0227e47f4daecf",
"view_tag": "dd"
}
}
}
],
"extra": [ 1, 237, 4, 59, 58, 77, 216, 233, 73, 132, 78, 46, 81, 159, 210, 119, 123, 14, 135, 176, 89, 86, 57, 148, 216, 99, 185, 166, 170, 161, 200, 187, 197, 2, 9, 0, 0, 0, 3, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}