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: daeef071c088d0c1b8ff43ae371b47953d0e27283e6de7c0e2b176a8134bce95
Tx prefix hash: c84debc376fb5d5f79ef6556d94f6d6812bfeffb4da7a9d9fc3864001d6db581
Tx public key: b3d9af0b38ba77aef8be7713ec017d5ce842df587f2a8649f085e01af6cd77cc
| Timestamp: 1780022338 | Timestamp [UTC]: 2026-05-29 02:38:58 | Age [y:d:h:m:s]: 00:011:00:01:38 |
| Block: 4152 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3745 | RingCT/type: yes/0 |
| Extra: 01b3d9af0b38ba77aef8be7713ec017d5ce842df587f2a8649f085e01af6cd77cc02090000001026697be300 | ||
1 output(s) for total of 34.906902797565 HMNY
| stealth address | amount | amount idx | tag |
| 00: f69d51db63ff0c908c82629e1b475519ba5b0cd9c2c386452dd7fbf73b89d3b3 | 34.906902797565 | 5183 of 0 | <bd> |
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": 4212,
"vin": [ {
"gen": {
"height": 4152
}
}
],
"vout": [ {
"amount": 34906902797565,
"target": {
"tagged_key": {
"key": "f69d51db63ff0c908c82629e1b475519ba5b0cd9c2c386452dd7fbf73b89d3b3",
"view_tag": "bd"
}
}
}
],
"extra": [ 1, 179, 217, 175, 11, 56, 186, 119, 174, 248, 190, 119, 19, 236, 1, 125, 92, 232, 66, 223, 88, 127, 42, 134, 73, 240, 133, 224, 26, 246, 205, 119, 204, 2, 9, 0, 0, 0, 16, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}