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: a0e1e0b1a8aa02bd4a9355088d331117c4e43dd1745c1504a9da39fe0b0638a5
Tx prefix hash: 8e0fcc3b6135f903da289a4809f7bd39c2c9f91d237f84293aa518da7db23dcd
Tx public key: 74e98e293ed3f7a4f275c742bd7910703ce5f8cefe2b3e5eafcfea9c43b104fc
| Timestamp: 1780994357 | Timestamp [UTC]: 2026-06-09 08:39:17 | Age [y:d:h:m:s]: 00:000:06:09:38 |
| Block: 8297 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 359 | RingCT/type: yes/0 |
| Extra: 0174e98e293ed3f7a4f275c742bd7910703ce5f8cefe2b3e5eafcfea9c43b104fc020900000001e49593ff00 | ||
1 output(s) for total of 34.632018001177 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2378e17b2438d12ddea7419173c0f44b8ea2b74002d5c17886d4d3a4999df133 | 34.632018001177 | 10265 of 0 | <73> |
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": 8357,
"vin": [ {
"gen": {
"height": 8297
}
}
],
"vout": [ {
"amount": 34632018001177,
"target": {
"tagged_key": {
"key": "2378e17b2438d12ddea7419173c0f44b8ea2b74002d5c17886d4d3a4999df133",
"view_tag": "73"
}
}
}
],
"extra": [ 1, 116, 233, 142, 41, 62, 211, 247, 164, 242, 117, 199, 66, 189, 121, 16, 112, 60, 229, 248, 206, 254, 43, 62, 94, 175, 207, 234, 156, 67, 177, 4, 252, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}