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: d6d6e8a8c3798cce84171f3239f28df57ebd31087f32f78d9f22b763ca87b76a
Tx prefix hash: ebea507d5e618abf813e9e770dc8969c7b75a773d93c532b35d968ad79d7aeb2
Tx public key: 4fd593cb4392824b54a941ad7dea9ccb60fe7fe029fbf2e20f50d9ddd210ebfd
| Timestamp: 1781001715 | Timestamp [UTC]: 2026-06-09 10:41:55 | Age [y:d:h:m:s]: 00:006:03:49:44 |
| Block: 8462 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 283 | RingCT/type: yes/0 |
| Extra: 014fd593cb4392824b54a941ad7dea9ccb60fe7fe029fbf2e20f50d9ddd210ebfd020900000001e49593ff00 | ||
1 output(s) for total of 34.621120575841 HMNY
| stealth address | amount | amount idx | tag |
| 00: b1c66948a321ef1dd1a8add505e30869473ff11116629d9f196575aa499261ec | 34.621120575841 | 10456 of 0 | <d9> |
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": 8522,
"vin": [ {
"gen": {
"height": 8462
}
}
],
"vout": [ {
"amount": 34621120575841,
"target": {
"tagged_key": {
"key": "b1c66948a321ef1dd1a8add505e30869473ff11116629d9f196575aa499261ec",
"view_tag": "d9"
}
}
}
],
"extra": [ 1, 79, 213, 147, 203, 67, 146, 130, 75, 84, 169, 65, 173, 125, 234, 156, 203, 96, 254, 127, 224, 41, 251, 242, 226, 15, 80, 217, 221, 210, 16, 235, 253, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}