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: 17300604e7dfcb9a338511f9b3dde8b9dac2a1d75c0233e307597bc3eb791e5e
Tx prefix hash: a6e4abfb6ee20a51718b3d7e53a1ce3deb663878485caa24e09270560e06975c
Tx public key: 269a32da7f987562a671bbd6e5eb4be485cd063e44df3cdc8475d366fd9b32ca
| Timestamp: 1780975541 | Timestamp [UTC]: 2026-06-09 03:25:41 | Age [y:d:h:m:s]: 00:000:08:01:07 |
| Block: 7929 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 584 | RingCT/type: yes/0 |
| Extra: 01269a32da7f987562a671bbd6e5eb4be485cd063e44df3cdc8475d366fd9b32ca020900000002e49593ff00 | ||
1 output(s) for total of 34.656334919688 HMNY
| stealth address | amount | amount idx | tag |
| 00: 21f0f76607e7a4559aae41e14d8d51599168f22096a97aafecb82ec14e017718 | 34.656334919688 | 9833 of 0 | <7a> |
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": 7989,
"vin": [ {
"gen": {
"height": 7929
}
}
],
"vout": [ {
"amount": 34656334919688,
"target": {
"tagged_key": {
"key": "21f0f76607e7a4559aae41e14d8d51599168f22096a97aafecb82ec14e017718",
"view_tag": "7a"
}
}
}
],
"extra": [ 1, 38, 154, 50, 218, 127, 152, 117, 98, 166, 113, 187, 214, 229, 235, 75, 228, 133, 205, 6, 62, 68, 223, 60, 220, 132, 117, 211, 102, 253, 155, 50, 202, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}