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: af19090f0031dde50abda8b71226f7a0f9fbd216fdd93c9bc9f1f7dcb058ffc4
Tx prefix hash: 7cf5f0d37f40711b48d7de2a3b488dcf3c54fcb9ccd23b687cc54271c25167a8
Tx public key: bed5280747cef39314a6a16ddfdb478fc48c0e2851f778149d7a402c33178b91
| Timestamp: 1779451834 | Timestamp [UTC]: 2026-05-22 12:10:34 | Age [y:d:h:m:s]: 00:017:13:25:23 |
| Block: 339 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7547 | RingCT/type: yes/0 |
| Extra: 01bed5280747cef39314a6a16ddfdb478fc48c0e2851f778149d7a402c33178b910209000000024438f87f00 | ||
1 output(s) for total of 35.161696581340 HMNY
| stealth address | amount | amount idx | tag |
| 00: bb1a328c2dfaa886ccb394c798bd8d68bed718e88e4e4c06774fc60574449700 | 35.161696581340 | 335 of 0 | <ae> |
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": 399,
"vin": [ {
"gen": {
"height": 339
}
}
],
"vout": [ {
"amount": 35161696581340,
"target": {
"tagged_key": {
"key": "bb1a328c2dfaa886ccb394c798bd8d68bed718e88e4e4c06774fc60574449700",
"view_tag": "ae"
}
}
}
],
"extra": [ 1, 190, 213, 40, 7, 71, 206, 243, 147, 20, 166, 161, 109, 223, 219, 71, 143, 196, 140, 14, 40, 81, 247, 120, 20, 157, 122, 64, 44, 51, 23, 139, 145, 2, 9, 0, 0, 0, 2, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}