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: 314a45fb62b9365acd8501b224bfe385a7be50c3d973fb46f6a46359f4f09e46
Tx prefix hash: 18c8019250f60aa357d09cdf149499f246b1d10d20bde47379ef8b2d0c57b839
Tx public key: d49c94f7024ae99d22fe042cd2da1b22f40dd5fc6274e4cb6afd3a17ae30aee1
| Timestamp: 1780841587 | Timestamp [UTC]: 2026-06-07 14:13:07 | Age [y:d:h:m:s]: 00:001:10:33:40 |
| Block: 7470 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 416 | RingCT/type: yes/0 |
| Extra: 01d49c94f7024ae99d22fe042cd2da1b22f40dd5fc6274e4cb6afd3a17ae30aee1020900000003e49593ff00 | ||
1 output(s) for total of 34.686688920031 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7ac8a9fcd321144a2b92b16a9c03cd93ccf7e261ab64d711ef23430ddfcfd200 | 34.686688920031 | 9202 of 0 | <18> |
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": 7530,
"vin": [ {
"gen": {
"height": 7470
}
}
],
"vout": [ {
"amount": 34686688920031,
"target": {
"tagged_key": {
"key": "7ac8a9fcd321144a2b92b16a9c03cd93ccf7e261ab64d711ef23430ddfcfd200",
"view_tag": "18"
}
}
}
],
"extra": [ 1, 212, 156, 148, 247, 2, 74, 233, 157, 34, 254, 4, 44, 210, 218, 27, 34, 244, 13, 213, 252, 98, 116, 228, 203, 106, 253, 58, 23, 174, 48, 174, 225, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}