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: 46e12b47b8e7921af17b494b098916a0139d15c2e5f1112d76973638ef24b3db
Tx prefix hash: f4d41b7f0ac19a74289846ec3a1e33b2c0f36b1a12777a0cc9baf50dacac4faa
Tx public key: 6fc0f395086d647d11a9dcbb2140c589d41417a43c5d1f0705afae5c1b532276
| Timestamp: 1779977855 | Timestamp [UTC]: 2026-05-28 14:17:35 | Age [y:d:h:m:s]: 00:011:11:18:22 |
| Block: 3901 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3985 | RingCT/type: yes/0 |
| Extra: 016fc0f395086d647d11a9dcbb2140c589d41417a43c5d1f0705afae5c1b53227602090000000526697be300 | ||
1 output(s) for total of 34.923618302380 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3f1df93e370798782ebb10e7dc1dead2caca957e833f3bd095f4c48c32dc706e | 34.923618302380 | 4779 of 0 | <47> |
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": 3961,
"vin": [ {
"gen": {
"height": 3901
}
}
],
"vout": [ {
"amount": 34923618302380,
"target": {
"tagged_key": {
"key": "3f1df93e370798782ebb10e7dc1dead2caca957e833f3bd095f4c48c32dc706e",
"view_tag": "47"
}
}
}
],
"extra": [ 1, 111, 192, 243, 149, 8, 109, 100, 125, 17, 169, 220, 187, 33, 64, 197, 137, 212, 20, 23, 164, 60, 93, 31, 7, 5, 175, 174, 92, 27, 83, 34, 118, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}