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: 0ebf94081781e3051163c925bd8756ac693d93f3757ebaad91b31430b718b4d5
Tx prefix hash: 547409e0ee3ad21b6094f0c72a5953be241b172bea675b6096efceb5fec7a488
Tx public key: 6e6bf30bef8c74cc30069007b33d96280c1d158a93deed25dbad0bcc81d773f4
| Timestamp: 1779847193 | Timestamp [UTC]: 2026-05-27 01:59:53 | Age [y:d:h:m:s]: 00:013:01:38:57 |
| Block: 2477 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5473 | RingCT/type: yes/0 |
| Extra: 016e6bf30bef8c74cc30069007b33d96280c1d158a93deed25dbad0bcc81d773f402090000000326697be300 | ||
1 output(s) for total of 35.018602123908 HMNY
| stealth address | amount | amount idx | tag |
| 00: 30d8038666d6797e89c2c32ad0dddb85767d973859eefdeec2cc2c1d96bdba13 | 35.018602123908 | 2913 of 0 | <a5> |
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": 2537,
"vin": [ {
"gen": {
"height": 2477
}
}
],
"vout": [ {
"amount": 35018602123908,
"target": {
"tagged_key": {
"key": "30d8038666d6797e89c2c32ad0dddb85767d973859eefdeec2cc2c1d96bdba13",
"view_tag": "a5"
}
}
}
],
"extra": [ 1, 110, 107, 243, 11, 239, 140, 116, 204, 48, 6, 144, 7, 179, 61, 150, 40, 12, 29, 21, 138, 147, 222, 237, 37, 219, 173, 11, 204, 129, 215, 115, 244, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}