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: 5bc8778ef9f07362a73eef671db03ddc4cb8c508aa0c66f6f39d4b02a2e351e3
Tx prefix hash: 2758d45ad7c153a01abbcd269ba744162a437d390f33be50669a7456fad2361f
Tx public key: 612245a9a775cf6dea38cbcc79c7d1d81dfbf9a92aba64266faf60664c48e4b1
| Timestamp: 1780692363 | Timestamp [UTC]: 2026-06-05 20:46:03 | Age [y:d:h:m:s]: 00:011:11:50:11 |
| Block: 5789 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2956 | RingCT/type: yes/0 |
| Extra: 01612245a9a775cf6dea38cbcc79c7d1d81dfbf9a92aba64266faf60664c48e4b1020900000002e49593ff00 | ||
1 output(s) for total of 34.798081809938 HMNY
| stealth address | amount | amount idx | tag |
| 00: 13378752cc7cfc5ffc6ea011ee10e1699cf5094d83f55718bf97330a8132c19b | 34.798081809938 | 7244 of 0 | <8b> |
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": 5849,
"vin": [ {
"gen": {
"height": 5789
}
}
],
"vout": [ {
"amount": 34798081809938,
"target": {
"tagged_key": {
"key": "13378752cc7cfc5ffc6ea011ee10e1699cf5094d83f55718bf97330a8132c19b",
"view_tag": "8b"
}
}
}
],
"extra": [ 1, 97, 34, 69, 169, 167, 117, 207, 109, 234, 56, 203, 204, 121, 199, 209, 216, 29, 251, 249, 169, 42, 186, 100, 38, 111, 175, 96, 102, 76, 72, 228, 177, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}