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: 2c0cce3c5a7c2f657fa486e3d34b93e6755f0e79e486fa0c8469b1cbb59a221d
Tx prefix hash: 4f6eb214b216b80ab52af0791e6ac0ece017590ca90ee75840f20be9e0925008
Tx public key: ee382559a372c1d832067384c0bef3b82011eaa5a70a91495e0ac66b85d38831
| Timestamp: 1780103530 | Timestamp [UTC]: 2026-05-30 01:12:10 | Age [y:d:h:m:s]: 00:018:06:53:11 |
| Block: 4840 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3905 | RingCT/type: yes/0 |
| Extra: 01ee382559a372c1d832067384c0bef3b82011eaa5a70a91495e0ac66b85d3883102090000000226697be300 | ||
1 output(s) for total of 34.863744408179 HMNY
| stealth address | amount | amount idx | tag |
| 00: d7be5211338c08c8578fea4e7cec862af4871edf69e761c0c6ea80c693694977 | 34.863744408179 | 6100 of 0 | <1a> |
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": 4900,
"vin": [ {
"gen": {
"height": 4840
}
}
],
"vout": [ {
"amount": 34863744408179,
"target": {
"tagged_key": {
"key": "d7be5211338c08c8578fea4e7cec862af4871edf69e761c0c6ea80c693694977",
"view_tag": "1a"
}
}
}
],
"extra": [ 1, 238, 56, 37, 89, 163, 114, 193, 216, 50, 6, 115, 132, 192, 190, 243, 184, 32, 17, 234, 165, 167, 10, 145, 73, 94, 10, 198, 107, 133, 211, 136, 49, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}