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: d2560ca5170fe92f5a1b8ed22f5947b22c6e378b1b91679ff38383b6d00f2755
Tx prefix hash: a84129104238646c58f0ef103bbe50f5f2a56e85db51756fd0cef338e34a9ed8
Tx public key: a10fee4a649f93a0496965698d67d1d2a9e1af1eef4c55fc4e068b9dec711d57
| Timestamp: 1779716562 | Timestamp [UTC]: 2026-05-25 13:42:42 | Age [y:d:h:m:s]: 00:014:13:07:06 |
| Block: 1656 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6244 | RingCT/type: yes/0 |
| Extra: 01a10fee4a649f93a0496965698d67d1d2a9e1af1eef4c55fc4e068b9dec711d57020900000003ba6d17be00 | ||
1 output(s) for total of 35.073481926732 HMNY
| stealth address | amount | amount idx | tag |
| 00: a54f60cc2e8c10aaf15e4057ef2dfa59af678caa339d2c15b1b69b2d61e677e9 | 35.073481926732 | 1820 of 0 | <ae> |
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": 1716,
"vin": [ {
"gen": {
"height": 1656
}
}
],
"vout": [ {
"amount": 35073481926732,
"target": {
"tagged_key": {
"key": "a54f60cc2e8c10aaf15e4057ef2dfa59af678caa339d2c15b1b69b2d61e677e9",
"view_tag": "ae"
}
}
}
],
"extra": [ 1, 161, 15, 238, 74, 100, 159, 147, 160, 73, 105, 101, 105, 141, 103, 209, 210, 169, 225, 175, 30, 239, 76, 85, 252, 78, 6, 139, 157, 236, 113, 29, 87, 2, 9, 0, 0, 0, 3, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}