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: 281f1e0eaad432c9b0a93a45d85932fccb9be98c7c3e6a001eaf7b78c85c4d9c
Tx prefix hash: b7738d9397c60496ccc6fc0d2e78478099e2d190a32682493b547b83404b7a65
Tx public key: ba76e8e5f692f59c3b3e60fece90eb113ae2e7170d7af8a5231ee0e809a90d19
| Timestamp: 1780046223 | Timestamp [UTC]: 2026-05-29 09:17:03 | Age [y:d:h:m:s]: 00:010:16:18:54 |
| Block: 4342 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3544 | RingCT/type: yes/0 |
| Extra: 01ba76e8e5f692f59c3b3e60fece90eb113ae2e7170d7af8a5231ee0e809a90d1902090000000626697be300 | ||
1 output(s) for total of 34.894254947076 HMNY
| stealth address | amount | amount idx | tag |
| 00: 37a9c5b5fcc023caa84173a1b74e793cb44532d0f5a36d488a0f527660998611 | 34.894254947076 | 5428 of 0 | <b3> |
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": 4402,
"vin": [ {
"gen": {
"height": 4342
}
}
],
"vout": [ {
"amount": 34894254947076,
"target": {
"tagged_key": {
"key": "37a9c5b5fcc023caa84173a1b74e793cb44532d0f5a36d488a0f527660998611",
"view_tag": "b3"
}
}
}
],
"extra": [ 1, 186, 118, 232, 229, 246, 146, 245, 156, 59, 62, 96, 254, 206, 144, 235, 17, 58, 226, 231, 23, 13, 122, 248, 165, 35, 30, 224, 232, 9, 169, 13, 25, 2, 9, 0, 0, 0, 6, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}