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: 6c7ee580bf618db8e578e247fbd763c4d5cecb36c5bdbc4d682d4532a51957bd
Tx prefix hash: fd6d7880ed7ce443d675abc4e06a6a84ebd52961be67ee279519d382d6f76e3e
Tx public key: 44f93bc6dc6bef1429a277196b55dcc6f3abd6d6716da9d0a73a34d90beffe84
| Timestamp: 1780972911 | Timestamp [UTC]: 2026-06-09 02:41:51 | Age [y:d:h:m:s]: 00:000:08:52:43 |
| Block: 7894 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 640 | RingCT/type: yes/0 |
| Extra: 0144f93bc6dc6bef1429a277196b55dcc6f3abd6d6716da9d0a73a34d90beffe84020900000003e49593ff00 | ||
1 output(s) for total of 34.658648559076 HMNY
| stealth address | amount | amount idx | tag |
| 00: 42c789f1f465f1ce74b4c612d5eb41812f1d6334ce4244e1de16cd05cfe6325e | 34.658648559076 | 9790 of 0 | <d9> |
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": 7954,
"vin": [ {
"gen": {
"height": 7894
}
}
],
"vout": [ {
"amount": 34658648559076,
"target": {
"tagged_key": {
"key": "42c789f1f465f1ce74b4c612d5eb41812f1d6334ce4244e1de16cd05cfe6325e",
"view_tag": "d9"
}
}
}
],
"extra": [ 1, 68, 249, 59, 198, 220, 107, 239, 20, 41, 162, 119, 25, 107, 85, 220, 198, 243, 171, 214, 214, 113, 109, 169, 208, 167, 58, 52, 217, 11, 239, 254, 132, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}