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: e826862be6b13291990bf85526dcf507514ef5fcaf0e62a6ac076d6c294d9f2f
Tx prefix hash: 61584d4de18f752c4aef56fd1a8b1381a39f7b7ccd4872bde097e35ab869bc15
Tx public key: f9c8bc7371f29a33a8e1f3b21ad87cc5a07df966e67fade0e7631fb0d6b8b4fc
| Timestamp: 1779954761 | Timestamp [UTC]: 2026-05-28 07:52:41 | Age [y:d:h:m:s]: 00:011:16:54:06 |
| Block: 3675 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4211 | RingCT/type: yes/0 |
| Extra: 01f9c8bc7371f29a33a8e1f3b21ad87cc5a07df966e67fade0e7631fb0d6b8b4fc02090000000626697be300 | ||
1 output(s) for total of 34.938675764378 HMNY
| stealth address | amount | amount idx | tag |
| 00: 47f8a508bf08c56b2bcf38f8dfe367b9846042cb7b647c959ff3232b257f09b2 | 34.938675764378 | 4442 of 0 | <cc> |
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": 3735,
"vin": [ {
"gen": {
"height": 3675
}
}
],
"vout": [ {
"amount": 34938675764378,
"target": {
"tagged_key": {
"key": "47f8a508bf08c56b2bcf38f8dfe367b9846042cb7b647c959ff3232b257f09b2",
"view_tag": "cc"
}
}
}
],
"extra": [ 1, 249, 200, 188, 115, 113, 242, 154, 51, 168, 225, 243, 178, 26, 216, 124, 197, 160, 125, 249, 102, 230, 127, 173, 224, 231, 99, 31, 176, 214, 184, 180, 252, 2, 9, 0, 0, 0, 6, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}