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: ac4d051f3c8c6fc7a5aa2de741dd537042bd5d27e31fe2e3d30c0cf1795a4c99
Tx prefix hash: 2f65345fbc5f71954d7b45024fce81f45fa07f3b59c9eac8ba17d2e76663c8ef
Tx public key: 83225567c9cd79e4fdcecd3fe68d4015cfbbe14afc22543b2dd80341df8a5986
| Timestamp: 1779846839 | Timestamp [UTC]: 2026-05-27 01:53:59 | Age [y:d:h:m:s]: 00:012:22:52:48 |
| Block: 2467 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5419 | RingCT/type: yes/0 |
| Extra: 0183225567c9cd79e4fdcecd3fe68d4015cfbbe14afc22543b2dd80341df8a598602090000000126697be300 | ||
1 output(s) for total of 35.019270057744 HMNY
| stealth address | amount | amount idx | tag |
| 00: d8cb37b357735cd73939ba841037098e3fd57783604963a41f5289f30cc28759 | 35.019270057744 | 2901 of 0 | <c9> |
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": 2527,
"vin": [ {
"gen": {
"height": 2467
}
}
],
"vout": [ {
"amount": 35019270057744,
"target": {
"tagged_key": {
"key": "d8cb37b357735cd73939ba841037098e3fd57783604963a41f5289f30cc28759",
"view_tag": "c9"
}
}
}
],
"extra": [ 1, 131, 34, 85, 103, 201, 205, 121, 228, 253, 206, 205, 63, 230, 141, 64, 21, 207, 187, 225, 74, 252, 34, 84, 59, 45, 216, 3, 65, 223, 138, 89, 134, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}