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: 1865bf00a4078692fb69a9b587ec6cd6aa4b70e5d8e7d6f8151f2170a213f914
Tx prefix hash: b50782fa7bc6a008a9478d9445c6ec2101d89cdb1f5e4c5ff3afcbadaa64ee46
Tx public key: 7bc47daeba987d65f9518703a6f3e1d73dfa52f0510a319e81617f9e9d28815a
| Timestamp: 1779727729 | Timestamp [UTC]: 2026-05-25 16:48:49 | Age [y:d:h:m:s]: 00:022:15:33:30 |
| Block: 1865 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6880 | RingCT/type: yes/0 |
| Extra: 017bc47daeba987d65f9518703a6f3e1d73dfa52f0510a319e81617f9e9d28815a020900000001ba6d17be00 | ||
1 output(s) for total of 35.059503152026 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2b83243179580f665cf8d3f09bca65a7a90cf54d89907a33f5efde710ab2e5ec | 35.059503152026 | 2070 of 0 | <d1> |
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": 1925,
"vin": [ {
"gen": {
"height": 1865
}
}
],
"vout": [ {
"amount": 35059503152026,
"target": {
"tagged_key": {
"key": "2b83243179580f665cf8d3f09bca65a7a90cf54d89907a33f5efde710ab2e5ec",
"view_tag": "d1"
}
}
}
],
"extra": [ 1, 123, 196, 125, 174, 186, 152, 125, 101, 249, 81, 135, 3, 166, 243, 225, 215, 61, 250, 82, 240, 81, 10, 49, 158, 129, 97, 127, 158, 157, 40, 129, 90, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}