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: 74a46812b89d7dc28e8f553d431fc9339c5ff2a6cb217aa018ead5258aae9add
Tx prefix hash: 70ba96bb7f6b2c12561d9be72bf172b3562c92e56128c175620a9bffc64ebfbe
Tx public key: 55f47697b28aeddae268951c4695184097a2ae380c79c84cc8f1e97f82ae8d01
| Timestamp: 1780825732 | Timestamp [UTC]: 2026-06-07 09:48:52 | Age [y:d:h:m:s]: 00:001:13:30:01 |
| Block: 7259 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 627 | RingCT/type: yes/0 |
| Extra: 0155f47697b28aeddae268951c4695184097a2ae380c79c84cc8f1e97f82ae8d01020900000002e49593ff00 | ||
1 output(s) for total of 34.700651420199 HMNY
| stealth address | amount | amount idx | tag |
| 00: 78ddaab7d13a5c95f26dd5b328dc6fbf73127d2c245b99f2ba0a345d455b3aa6 | 34.700651420199 | 8937 of 0 | <d8> |
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": 7319,
"vin": [ {
"gen": {
"height": 7259
}
}
],
"vout": [ {
"amount": 34700651420199,
"target": {
"tagged_key": {
"key": "78ddaab7d13a5c95f26dd5b328dc6fbf73127d2c245b99f2ba0a345d455b3aa6",
"view_tag": "d8"
}
}
}
],
"extra": [ 1, 85, 244, 118, 151, 178, 138, 237, 218, 226, 104, 149, 28, 70, 149, 24, 64, 151, 162, 174, 56, 12, 121, 200, 76, 200, 241, 233, 127, 130, 174, 141, 1, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}