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: 778c2d0f298bef30d4849d39e979a36a629104fbf5240426dc09b0e3a48925ed
Tx prefix hash: cc67c9b5ae97a46166d71ae0dcd68a9f8d74130d157224fe3d2dc62314d0fd34
Tx public key: a8559a69f6069dc7ec0e90a4e334635162ec14fd1ad539c8dbea5ddc9f6e1a64
| Timestamp: 1779966458 | Timestamp [UTC]: 2026-05-28 11:07:38 | Age [y:d:h:m:s]: 00:011:15:32:58 |
| Block: 3808 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4088 | RingCT/type: yes/0 |
| Extra: 01a8559a69f6069dc7ec0e90a4e334635162ec14fd1ad539c8dbea5ddc9f6e1a6402090000000326697be300 | ||
1 output(s) for total of 34.929813728708 HMNY
| stealth address | amount | amount idx | tag |
| 00: 244144626de2c0a3a6b073a3fed807e01dc36bd6c794e5279a4fab8a259d12b9 | 34.929813728708 | 4634 of 0 | <d9> |
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": 3868,
"vin": [ {
"gen": {
"height": 3808
}
}
],
"vout": [ {
"amount": 34929813728708,
"target": {
"tagged_key": {
"key": "244144626de2c0a3a6b073a3fed807e01dc36bd6c794e5279a4fab8a259d12b9",
"view_tag": "d9"
}
}
}
],
"extra": [ 1, 168, 85, 154, 105, 246, 6, 157, 199, 236, 14, 144, 164, 227, 52, 99, 81, 98, 236, 20, 253, 26, 213, 57, 200, 219, 234, 93, 220, 159, 110, 26, 100, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}