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: d5b67227262159edeb150ca6b852f606ee2d1c885fde22f22fa6e1e3b002b002
Tx prefix hash: 02a4d2c7313967074fc91eaf9793e843162c4fd8cd49f533d79765eba6e80c7f
Tx public key: 8dc37b57d4434c72a5069c7d7698f014753855228ac5d24a495130933b8b6234
| Timestamp: 1780701882 | Timestamp [UTC]: 2026-06-05 23:24:42 | Age [y:d:h:m:s]: 00:003:00:58:27 |
| Block: 6066 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1820 | RingCT/type: yes/0 |
| Extra: 018dc37b57d4434c72a5069c7d7698f014753855228ac5d24a495130933b8b6234020900000001e49593ff00 | ||
1 output(s) for total of 34.779701583868 HMNY
| stealth address | amount | amount idx | tag |
| 00: 566d2f3648b290eeb68c0a1685e29cc1ea3d298eeb34c0fe7316191d55fe3e6f | 34.779701583868 | 7537 of 0 | <63> |
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": 6126,
"vin": [ {
"gen": {
"height": 6066
}
}
],
"vout": [ {
"amount": 34779701583868,
"target": {
"tagged_key": {
"key": "566d2f3648b290eeb68c0a1685e29cc1ea3d298eeb34c0fe7316191d55fe3e6f",
"view_tag": "63"
}
}
}
],
"extra": [ 1, 141, 195, 123, 87, 212, 67, 76, 114, 165, 6, 156, 125, 118, 152, 240, 20, 117, 56, 85, 34, 138, 197, 210, 74, 73, 81, 48, 147, 59, 139, 98, 52, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}