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: 86bfbb0add4a546c1404d2371ca64b7a3c285648a26366dae33c9176d06328ef
Tx prefix hash: 5dde3234715fe3bfbe79f8890bfec8da7445f02f6e04472472ae6d07626e2b27
Tx public key: 30ed45884ec945f8f6e357f4acc2b4e6f2f35ac1defa1b72fa422df246d970ed
| Timestamp: 1780689367 | Timestamp [UTC]: 2026-06-05 19:56:07 | Age [y:d:h:m:s]: 00:003:05:39:50 |
| Block: 5590 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2296 | RingCT/type: yes/0 |
| Extra: 0130ed45884ec945f8f6e357f4acc2b4e6f2f35ac1defa1b72fa422df246d970ed020900000002e49593ff00 | ||
1 output(s) for total of 34.811292372173 HMNY
| stealth address | amount | amount idx | tag |
| 00: 31cdd3ef2bffc19585d05fecdf134e3d09a1fc51103f5d50eb7a53dba8433063 | 34.811292372173 | 7035 of 0 | <39> |
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": 5650,
"vin": [ {
"gen": {
"height": 5590
}
}
],
"vout": [ {
"amount": 34811292372173,
"target": {
"tagged_key": {
"key": "31cdd3ef2bffc19585d05fecdf134e3d09a1fc51103f5d50eb7a53dba8433063",
"view_tag": "39"
}
}
}
],
"extra": [ 1, 48, 237, 69, 136, 78, 201, 69, 248, 246, 227, 87, 244, 172, 194, 180, 230, 242, 243, 90, 193, 222, 250, 27, 114, 250, 66, 45, 242, 70, 217, 112, 237, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}