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: ce8330cb8e9f51f39904bf1e8e2e5be91b07ba5b08f1df4ba565d0e5c9ed59ac
Tx prefix hash: ba75ba61aabf5eea949c683df8da75a887862d10fd6e2d07a6e258693f1c866f
Tx public key: 9f503b1af0efbdcc5a05992b4b632897fd720fb43b78601cf729dc9fe7564f0f
| Timestamp: 1780741254 | Timestamp [UTC]: 2026-06-06 10:20:54 | Age [y:d:h:m:s]: 00:002:14:25:53 |
| Block: 6411 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1475 | RingCT/type: yes/0 |
| Extra: 019f503b1af0efbdcc5a05992b4b632897fd720fb43b78601cf729dc9fe7564f0f020900000002e49593ff00 | ||
1 output(s) for total of 34.756822819780 HMNY
| stealth address | amount | amount idx | tag |
| 00: e8ca6792042763eb3d387a7abb046168b28d1786f1a75fa1317912e966a66cd3 | 34.756822819780 | 7902 of 0 | <fb> |
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": 6471,
"vin": [ {
"gen": {
"height": 6411
}
}
],
"vout": [ {
"amount": 34756822819780,
"target": {
"tagged_key": {
"key": "e8ca6792042763eb3d387a7abb046168b28d1786f1a75fa1317912e966a66cd3",
"view_tag": "fb"
}
}
}
],
"extra": [ 1, 159, 80, 59, 26, 240, 239, 189, 204, 90, 5, 153, 43, 75, 99, 40, 151, 253, 114, 15, 180, 59, 120, 96, 28, 247, 41, 220, 159, 231, 86, 79, 15, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}