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: acd368788543d66014b07af6ac3c31dac3203979baeadec19612bf0d2e8a71f7
Tx prefix hash: ac81946cdbfde87f694232b8a452dc277cc5e99ea6616c9fee1777db67fbafbb
Tx public key: db21ba238e718c694574821a07ee04fdca28c26f29654d7bad1c3cf6b93dd542
| Timestamp: 1780721284 | Timestamp [UTC]: 2026-06-06 04:48:04 | Age [y:d:h:m:s]: 00:002:18:30:49 |
| Block: 6248 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1638 | RingCT/type: yes/0 |
| Extra: 01db21ba238e718c694574821a07ee04fdca28c26f29654d7bad1c3cf6b93dd542020900000003e49593ff00 | ||
1 output(s) for total of 34.767630330709 HMNY
| stealth address | amount | amount idx | tag |
| 00: bb5b51408e5bfa8adc249f5e02644797d7e15d5977179762d18d59d77aa6b71d | 34.767630330709 | 7729 of 0 | <a3> |
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": 6308,
"vin": [ {
"gen": {
"height": 6248
}
}
],
"vout": [ {
"amount": 34767630330709,
"target": {
"tagged_key": {
"key": "bb5b51408e5bfa8adc249f5e02644797d7e15d5977179762d18d59d77aa6b71d",
"view_tag": "a3"
}
}
}
],
"extra": [ 1, 219, 33, 186, 35, 142, 113, 140, 105, 69, 116, 130, 26, 7, 238, 4, 253, 202, 40, 194, 111, 41, 101, 77, 123, 173, 28, 60, 246, 185, 61, 213, 66, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}