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: a261f3e31f1ffd5d476a36730800e8e23631acd38c1104f9fd9359eac3e721da
Tx prefix hash: 6b4fca5fefb9a5ff29fdc7ad0ad8a0a9b18f03f6299d3e67a857d9347c4cfcfa
Tx public key: f50e8377638af01c960432276b184f31ec9560c4f0b7b0d165254ca4e4663fbc
| Timestamp: 1780825484 | Timestamp [UTC]: 2026-06-07 09:44:44 | Age [y:d:h:m:s]: 00:008:02:55:25 |
| Block: 7252 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1493 | RingCT/type: yes/0 |
| Extra: 01f50e8377638af01c960432276b184f31ec9560c4f0b7b0d165254ca4e4663fbc020900000001e49593ff00 | ||
1 output(s) for total of 34.701114727414 HMNY
| stealth address | amount | amount idx | tag |
| 00: d772b3d0cff1d5539d0e042703a12e45bb4a4848961ab666d0070478f54331bf | 34.701114727414 | 8930 of 0 | <77> |
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": 7312,
"vin": [ {
"gen": {
"height": 7252
}
}
],
"vout": [ {
"amount": 34701114727414,
"target": {
"tagged_key": {
"key": "d772b3d0cff1d5539d0e042703a12e45bb4a4848961ab666d0070478f54331bf",
"view_tag": "77"
}
}
}
],
"extra": [ 1, 245, 14, 131, 119, 99, 138, 240, 28, 150, 4, 50, 39, 107, 24, 79, 49, 236, 149, 96, 196, 240, 183, 176, 209, 101, 37, 76, 164, 228, 102, 63, 188, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}