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: b44d63ef6041e6133203e9e8b8491e829a8e79f2e0db8c84ed5af6055e5c6c58
Tx prefix hash: 0a0d2e52e23ef25a9a8c51d7060e142f100b3510ff492eb5ac4cbf772f2bbe60
Tx public key: d8122bd17960dcd89473c8cf53621b237cb864a06dad29f450d8e016d088d875
| Timestamp: 1779874008 | Timestamp [UTC]: 2026-05-27 09:26:48 | Age [y:d:h:m:s]: 00:012:16:09:09 |
| Block: 2852 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5034 | RingCT/type: yes/0 |
| Extra: 01d8122bd17960dcd89473c8cf53621b237cb864a06dad29f450d8e016d088d87502090000000226697be300 | ||
1 output(s) for total of 34.993563799418 HMNY
| stealth address | amount | amount idx | tag |
| 00: 10366eeb2050176867e5939f187e08476665663e9afc94c9dbcae65e470f4e2b | 34.993563799418 | 3376 of 0 | <83> |
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": 2912,
"vin": [ {
"gen": {
"height": 2852
}
}
],
"vout": [ {
"amount": 34993563799418,
"target": {
"tagged_key": {
"key": "10366eeb2050176867e5939f187e08476665663e9afc94c9dbcae65e470f4e2b",
"view_tag": "83"
}
}
}
],
"extra": [ 1, 216, 18, 43, 209, 121, 96, 220, 216, 148, 115, 200, 207, 83, 98, 27, 35, 124, 184, 100, 160, 109, 173, 41, 244, 80, 216, 224, 22, 208, 136, 216, 117, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}