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: 6ca5bed6d3dd51c3d466fcab62ed075dfefce12155f729ad3fffdf99e1b5e63f
Tx prefix hash: cb529c331847401bc95f8032a11170af343e1b471a8cb6e9e5cb73d04d0c9ff0
Tx public key: 2bbb0e595e11c8445e3826d818a0a637c3bb40d974fbe3591ad33ad91efba693
| Timestamp: 1780038640 | Timestamp [UTC]: 2026-05-29 07:10:40 | Age [y:d:h:m:s]: 00:011:09:58:23 |
| Block: 4262 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4471 | RingCT/type: yes/0 |
| Extra: 012bbb0e595e11c8445e3826d818a0a637c3bb40d974fbe3591ad33ad91efba69302090000000526697be300 | ||
1 output(s) for total of 34.902195799155 HMNY
| stealth address | amount | amount idx | tag |
| 00: ca3c779a829b232b6546a0074267728b7cb03f8759f2a3ccc91efaa6dc9cbba9 | 34.902195799155 | 5321 of 0 | <6d> |
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": 4322,
"vin": [ {
"gen": {
"height": 4262
}
}
],
"vout": [ {
"amount": 34902195799155,
"target": {
"tagged_key": {
"key": "ca3c779a829b232b6546a0074267728b7cb03f8759f2a3ccc91efaa6dc9cbba9",
"view_tag": "6d"
}
}
}
],
"extra": [ 1, 43, 187, 14, 89, 94, 17, 200, 68, 94, 56, 38, 216, 24, 160, 166, 55, 195, 187, 64, 217, 116, 251, 227, 89, 26, 211, 58, 217, 30, 251, 166, 147, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}