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: bc4510583640f3ac65d3a84284c7bfce2b2dcc7d3992bcf1173963590c8f05bb
Tx prefix hash: e647c2b976b31f634482bd743ea78bad38fd70e1255877f5ce01af719f8c46a8
Tx public key: 1b9bd59438b9ad4d59b9239e29c44c4535dacaac94eba400b36642833e2fcc19
| Timestamp: 1780841891 | Timestamp [UTC]: 2026-06-07 14:18:11 | Age [y:d:h:m:s]: 00:002:02:50:52 |
| Block: 7473 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1262 | RingCT/type: yes/0 |
| Extra: 011b9bd59438b9ad4d59b9239e29c44c4535dacaac94eba400b36642833e2fcc19020900000002e49593ff00 | ||
1 output(s) for total of 34.686490441583 HMNY
| stealth address | amount | amount idx | tag |
| 00: acb6a123c9adb45a1ea28d42c92daf24dfd1b3f3c2019a822bb6395cbe837e5f | 34.686490441583 | 9205 of 0 | <49> |
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": 7533,
"vin": [ {
"gen": {
"height": 7473
}
}
],
"vout": [ {
"amount": 34686490441583,
"target": {
"tagged_key": {
"key": "acb6a123c9adb45a1ea28d42c92daf24dfd1b3f3c2019a822bb6395cbe837e5f",
"view_tag": "49"
}
}
}
],
"extra": [ 1, 27, 155, 213, 148, 56, 185, 173, 77, 89, 185, 35, 158, 41, 196, 76, 69, 53, 218, 202, 172, 148, 235, 164, 0, 179, 102, 66, 131, 62, 47, 204, 25, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}