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: 9d81df9198076532b387806babf676627a0e153918c0fea8edd551e42ba54ba0
Tx prefix hash: 052b575884803798e1ce0b2b90193c05730fbba4877b457c80aefe3bf7095d3f
Tx public key: b719b89a6bbda482890b73554b76d6d7f5caf3978d428ebd0b53dd76cebb051d
| Timestamp: 1779952322 | Timestamp [UTC]: 2026-05-28 07:12:02 | Age [y:d:h:m:s]: 00:011:16:06:51 |
| Block: 3637 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4249 | RingCT/type: yes/0 |
| Extra: 01b719b89a6bbda482890b73554b76d6d7f5caf3978d428ebd0b53dd76cebb051d02090000000326697be300 | ||
1 output(s) for total of 34.944619787513 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3ef2d183c990375d0b4079f98ed3d4b67c105909ccfc401c5ac4419c0e822677 | 34.944619787513 | 4393 of 0 | <9e> |
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": 3697,
"vin": [ {
"gen": {
"height": 3637
}
}
],
"vout": [ {
"amount": 34944619787513,
"target": {
"tagged_key": {
"key": "3ef2d183c990375d0b4079f98ed3d4b67c105909ccfc401c5ac4419c0e822677",
"view_tag": "9e"
}
}
}
],
"extra": [ 1, 183, 25, 184, 154, 107, 189, 164, 130, 137, 11, 115, 85, 75, 118, 214, 215, 245, 202, 243, 151, 141, 66, 142, 189, 11, 83, 221, 118, 206, 187, 5, 29, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}