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: 44270d6c4314491b20b23f4fdaf661596bdc6f02d3e50caa5458439a4b87ab5b
Tx prefix hash: bee9576ad86176a1edccfbf26b8c1e3d35a5fb36d2d6c5eddc21c693cbea5cda
Tx public key: c47fb56c7bbc497804280786818cf23351f33b560a071524532d5d49f20b3668
| Timestamp: 1779993073 | Timestamp [UTC]: 2026-05-28 18:31:13 | Age [y:d:h:m:s]: 00:011:09:19:45 |
| Block: 4004 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3963 | RingCT/type: yes/0 |
| Extra: 01c47fb56c7bbc497804280786818cf23351f33b560a071524532d5d49f20b366802090000000226697be300 | ||
1 output(s) for total of 34.916757983629 HMNY
| stealth address | amount | amount idx | tag |
| 00: c93fee0812eab523c6c2fa58ad6dcab07c855913e21680cd3250c2e6ad52d8b3 | 34.916757983629 | 4950 of 0 | <ac> |
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": 4064,
"vin": [ {
"gen": {
"height": 4004
}
}
],
"vout": [ {
"amount": 34916757983629,
"target": {
"tagged_key": {
"key": "c93fee0812eab523c6c2fa58ad6dcab07c855913e21680cd3250c2e6ad52d8b3",
"view_tag": "ac"
}
}
}
],
"extra": [ 1, 196, 127, 181, 108, 123, 188, 73, 120, 4, 40, 7, 134, 129, 140, 242, 51, 81, 243, 59, 86, 10, 7, 21, 36, 83, 45, 93, 73, 242, 11, 54, 104, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}