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: 08c9038259c59b90074671765fe9958e3aabd2b7332582c43b4875b8584b6377
Tx prefix hash: 4807e9c18e5597c3d31dd8c63a950042c841194e4265d6b8c4a618b0b5f561c4
Tx public key: d905462c18ccc9e7fb29c130923b4d7ab29d0a96682493d198c19b6a4b4db6ad
| Timestamp: 1780136944 | Timestamp [UTC]: 2026-05-30 10:29:04 | Age [y:d:h:m:s]: 00:009:12:49:49 |
| Block: 4969 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2917 | RingCT/type: yes/0 |
| Extra: 01d905462c18ccc9e7fb29c130923b4d7ab29d0a96682493d198c19b6a4b4db6ad02090000000226697be300 | ||
1 output(s) for total of 34.859160345741 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9b2b3cdec4b497450ed07b4104afa1adfd94d82ba67eb3948f5e06d236f43724 | 34.859160345741 | 6320 of 0 | <25> |
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": 5029,
"vin": [ {
"gen": {
"height": 4969
}
}
],
"vout": [ {
"amount": 34859160345741,
"target": {
"tagged_key": {
"key": "9b2b3cdec4b497450ed07b4104afa1adfd94d82ba67eb3948f5e06d236f43724",
"view_tag": "25"
}
}
}
],
"extra": [ 1, 217, 5, 70, 44, 24, 204, 201, 231, 251, 41, 193, 48, 146, 59, 77, 122, 178, 157, 10, 150, 104, 36, 147, 209, 152, 193, 155, 106, 75, 77, 182, 173, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}