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: bcdc99e152781925304e8df028f0ba74b6338bc62918bc1030db629cef7aa3fa
Tx prefix hash: f3a22c6c987a62f683266c7ac557ba407c46f992f0939f42484bd29e3fcb7c47
Tx public key: 2addead442dee9b5458cbe70fa84ecd4ef4276f051c9c2febcd20e7fae6467fb
| Timestamp: 1779889607 | Timestamp [UTC]: 2026-05-27 13:46:47 | Age [y:d:h:m:s]: 00:012:14:46:15 |
| Block: 3051 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4974 | RingCT/type: yes/0 |
| Extra: 012addead442dee9b5458cbe70fa84ecd4ef4276f051c9c2febcd20e7fae6467fb02090000000126697be300 | ||
1 output(s) for total of 34.980284066869 HMNY
| stealth address | amount | amount idx | tag |
| 00: 61310ddae69cecc23c3d135b0715eebe10daa3c83cc4ff2b5aa651083e937725 | 34.980284066869 | 3627 of 0 | <e5> |
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": 3111,
"vin": [ {
"gen": {
"height": 3051
}
}
],
"vout": [ {
"amount": 34980284066869,
"target": {
"tagged_key": {
"key": "61310ddae69cecc23c3d135b0715eebe10daa3c83cc4ff2b5aa651083e937725",
"view_tag": "e5"
}
}
}
],
"extra": [ 1, 42, 221, 234, 212, 66, 222, 233, 181, 69, 140, 190, 112, 250, 132, 236, 212, 239, 66, 118, 240, 81, 201, 194, 254, 188, 210, 14, 127, 174, 100, 103, 251, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}