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: 109494576bdec2738d55a78c86704640ebc2237594a16f267fa05f71491bc668
Tx prefix hash: cb446395764ddb84a69213ca4759aeac3a41d3dc81022390ea0e217d24766f49
Tx public key: be2904d1ca004b287ec843d6aa12f332cbac22f72f7d8883754e4ad6d9f09e45
| Timestamp: 1780890410 | Timestamp [UTC]: 2026-06-08 03:46:50 | Age [y:d:h:m:s]: 00:000:23:02:58 |
| Block: 7716 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 183 | RingCT/type: yes/0 |
| Extra: 01be2904d1ca004b287ec843d6aa12f332cbac22f72f7d8883754e4ad6d9f09e450209000000034a728a4c00 | ||
1 output(s) for total of 34.670417458422 HMNY
| stealth address | amount | amount idx | tag |
| 00: 48d69e753ce3b0c2e9dbde0333c77c106095d38ace8064f4cf8c897df08ffd33 | 34.670417458422 | 9550 of 0 | <d6> |
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": 7776,
"vin": [ {
"gen": {
"height": 7716
}
}
],
"vout": [ {
"amount": 34670417458422,
"target": {
"tagged_key": {
"key": "48d69e753ce3b0c2e9dbde0333c77c106095d38ace8064f4cf8c897df08ffd33",
"view_tag": "d6"
}
}
}
],
"extra": [ 1, 190, 41, 4, 209, 202, 0, 75, 40, 126, 200, 67, 214, 170, 18, 243, 50, 203, 172, 34, 247, 47, 125, 136, 131, 117, 78, 74, 214, 217, 240, 158, 69, 2, 9, 0, 0, 0, 3, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}