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: 5b6894e6c9026991d3b7643f59957ca2691cfcc37fc25e322fc5e3cdcea1fdec
Tx prefix hash: 267aea27aafe78ca42f723a3ffc64d99b6c8f8302e316c2db474ecdafcdc5f62
Tx public key: bf0c0c46a2573ef4d4f930bb5fbb74d80707a3b33526d0865fb40cb2f2fb41a3
| Timestamp: 1780822266 | Timestamp [UTC]: 2026-06-07 08:51:06 | Age [y:d:h:m:s]: 00:008:03:49:03 |
| Block: 7196 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1549 | RingCT/type: yes/0 |
| Extra: 01bf0c0c46a2573ef4d4f930bb5fbb74d80707a3b33526d0865fb40cb2f2fb41a3020900000001e49593ff00 | ||
1 output(s) for total of 34.704821407833 HMNY
| stealth address | amount | amount idx | tag |
| 00: 84f2a572c0b7595eab01a2661d885bbb6c6d8dce2703616d228f7fd1300c11e0 | 34.704821407833 | 8864 of 0 | <3e> |
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": 7256,
"vin": [ {
"gen": {
"height": 7196
}
}
],
"vout": [ {
"amount": 34704821407833,
"target": {
"tagged_key": {
"key": "84f2a572c0b7595eab01a2661d885bbb6c6d8dce2703616d228f7fd1300c11e0",
"view_tag": "3e"
}
}
}
],
"extra": [ 1, 191, 12, 12, 70, 162, 87, 62, 244, 212, 249, 48, 187, 95, 187, 116, 216, 7, 7, 163, 179, 53, 38, 208, 134, 95, 180, 12, 178, 242, 251, 65, 163, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}