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: 1c4bea00817b3345e8229d784fa3fcb12d68ecd36f9821c25459da920098f1e1
Tx prefix hash: 4b3b2310a5556f9f29058925b8a7492b0516044b2749de3e7a110e5d20129d7c
Tx public key: 9f89e8702d0df79ad3787976d985858fdb6601ab7f308c949c36c36cbbd9e7f1
| Timestamp: 1780893291 | Timestamp [UTC]: 2026-06-08 04:34:51 | Age [y:d:h:m:s]: 00:000:22:05:45 |
| Block: 7743 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 154 | RingCT/type: yes/0 |
| Extra: 019f89e8702d0df79ad3787976d985858fdb6601ab7f308c949c36c36cbbd9e7f10209000000014a728a4c00 | ||
1 output(s) for total of 34.668632031213 HMNY
| stealth address | amount | amount idx | tag |
| 00: d99f28b7b7ec948791a03459b600e483f0a82a85f281fc107578ac208ab8200e | 34.668632031213 | 9587 of 0 | <77> |
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": 7803,
"vin": [ {
"gen": {
"height": 7743
}
}
],
"vout": [ {
"amount": 34668632031213,
"target": {
"tagged_key": {
"key": "d99f28b7b7ec948791a03459b600e483f0a82a85f281fc107578ac208ab8200e",
"view_tag": "77"
}
}
}
],
"extra": [ 1, 159, 137, 232, 112, 45, 13, 247, 154, 211, 120, 121, 118, 217, 133, 133, 143, 219, 102, 1, 171, 127, 48, 140, 148, 156, 54, 195, 108, 187, 217, 231, 241, 2, 9, 0, 0, 0, 1, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}