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: 330857c73a017b0f6cde40c64c111b93f8f134a3521e4bbd500063a737e34f84
Tx prefix hash: d8fd802d18fb9bf03e860ad3bfbed1017cf2ab2a622c223083f5bb019eefe2ef
Tx public key: 746659b9f06b4c08effe734fa0f109cda39473af0a74e55acaa533dfb08183f0
| Timestamp: 1780689350 | Timestamp [UTC]: 2026-06-05 19:55:50 | Age [y:d:h:m:s]: 00:003:06:44:46 |
| Block: 5588 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2309 | RingCT/type: yes/0 |
| Extra: 01746659b9f06b4c08effe734fa0f109cda39473af0a74e55acaa533dfb08183f0020900000001e49593ff00 | ||
1 output(s) for total of 34.811425167095 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9d64d2d13c3d7ec1398e334be9be54465d7d705292a4d3621114be07b0126629 | 34.811425167095 | 7033 of 0 | <ec> |
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": 5648,
"vin": [ {
"gen": {
"height": 5588
}
}
],
"vout": [ {
"amount": 34811425167095,
"target": {
"tagged_key": {
"key": "9d64d2d13c3d7ec1398e334be9be54465d7d705292a4d3621114be07b0126629",
"view_tag": "ec"
}
}
}
],
"extra": [ 1, 116, 102, 89, 185, 240, 107, 76, 8, 239, 254, 115, 79, 160, 241, 9, 205, 163, 148, 115, 175, 10, 116, 229, 90, 202, 165, 51, 223, 176, 129, 131, 240, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}