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: 9a69b8a43df90c948efeb9ebe853f5164f6734e54887eb4b5b59a06c85d16323
Tx prefix hash: 618c672929c4d17e0e89e94b91cc59315fa45f75ff3299da10cae8b7b1927681
Tx public key: 012f83e67ea8e0ddcc658a0c760e97eb42526937f6424a405e23886bb8591fe4
| Timestamp: 1779647532 | Timestamp [UTC]: 2026-05-24 18:32:12 | Age [y:d:h:m:s]: 00:015:07:03:45 |
| Block: 1461 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6425 | RingCT/type: yes/0 |
| Extra: 01012f83e67ea8e0ddcc658a0c760e97eb42526937f6424a405e23886bb8591fe4020900000001ba6d17be00 | ||
1 output(s) for total of 35.086529350180 HMNY
| stealth address | amount | amount idx | tag |
| 00: 79f0986834a0ea04a33524121e67bb935af6786177c6734c2cc4ca0f579c9555 | 35.086529350180 | 1615 of 0 | <a6> |
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": 1521,
"vin": [ {
"gen": {
"height": 1461
}
}
],
"vout": [ {
"amount": 35086529350180,
"target": {
"tagged_key": {
"key": "79f0986834a0ea04a33524121e67bb935af6786177c6734c2cc4ca0f579c9555",
"view_tag": "a6"
}
}
}
],
"extra": [ 1, 1, 47, 131, 230, 126, 168, 224, 221, 204, 101, 138, 12, 118, 14, 151, 235, 66, 82, 105, 55, 246, 66, 74, 64, 94, 35, 136, 107, 184, 89, 31, 228, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}