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: 1372e9813d24394f2691dd3a160c7c64ccf49bf4539add116d900959f68a3dc3
Tx prefix hash: 7be32aa014119078169f21dc39ccb8f2f6e18c33867f3fb738c8eef025ce13e3
Tx public key: 0de02e9c37c8fb0acf2e1093940923f3daea8afb10147d4389c39664f1b5a6d6
| Timestamp: 1780814276 | Timestamp [UTC]: 2026-06-07 06:37:56 | Age [y:d:h:m:s]: 00:001:16:40:57 |
| Block: 7032 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 854 | RingCT/type: yes/0 |
| Extra: 010de02e9c37c8fb0acf2e1093940923f3daea8afb10147d4389c39664f1b5a6d6020900000002e49593ff00 | ||
1 output(s) for total of 34.715678964010 HMNY
| stealth address | amount | amount idx | tag |
| 00: a48805c08071e505e5bc61a7ccef2fe9054f078e36b3ad7e562317435d45c67c | 34.715678964010 | 8672 of 0 | <f9> |
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": 7092,
"vin": [ {
"gen": {
"height": 7032
}
}
],
"vout": [ {
"amount": 34715678964010,
"target": {
"tagged_key": {
"key": "a48805c08071e505e5bc61a7ccef2fe9054f078e36b3ad7e562317435d45c67c",
"view_tag": "f9"
}
}
}
],
"extra": [ 1, 13, 224, 46, 156, 55, 200, 251, 10, 207, 46, 16, 147, 148, 9, 35, 243, 218, 234, 138, 251, 16, 20, 125, 67, 137, 195, 150, 100, 241, 181, 166, 214, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}