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: 3a715db9da7af1900f48ccd28a55eef24a5564299dd0e9d746b387c020b0360b
Tx prefix hash: 243e43c5ca64c39ab849a9d28880b541e5daeca01ff930eaacae8adff28949ec
Tx public key: e032974d7669a9f25d1f94c8ad4993d37000b322eb198d562a63e93958ff9a6f
| Timestamp: 1780998256 | Timestamp [UTC]: 2026-06-09 09:44:16 | Age [y:d:h:m:s]: 00:007:23:19:41 |
| Block: 8391 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 354 | RingCT/type: yes/0 |
| Extra: 01e032974d7669a9f25d1f94c8ad4993d37000b322eb198d562a63e93958ff9a6f020900000001e49593ff00 | ||
1 output(s) for total of 34.625809350624 HMNY
| stealth address | amount | amount idx | tag |
| 00: db031adbd58a7b967aa72d97867db00c6d33dff4243cdf78a9b8c9d9c7c9d5b9 | 34.625809350624 | 10373 of 0 | <61> |
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": 8451,
"vin": [ {
"gen": {
"height": 8391
}
}
],
"vout": [ {
"amount": 34625809350624,
"target": {
"tagged_key": {
"key": "db031adbd58a7b967aa72d97867db00c6d33dff4243cdf78a9b8c9d9c7c9d5b9",
"view_tag": "61"
}
}
}
],
"extra": [ 1, 224, 50, 151, 77, 118, 105, 169, 242, 93, 31, 148, 200, 173, 73, 147, 211, 112, 0, 179, 34, 235, 25, 141, 86, 42, 99, 233, 57, 88, 255, 154, 111, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}