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: b095e9d51dc422a588cc5ae1193d8cd86f97ce2a22fc0832d95a8cd3e4c1b818
Tx prefix hash: a314d5e087dd86326df809bf22d6c8d064a41b841148ea600f91c177d9942a96
Tx public key: f9eeae7b290711040d5845e0c7a9918995c0604a3f9aeb034f0d14317f38a02f
| Timestamp: 1779933440 | Timestamp [UTC]: 2026-05-28 01:57:20 | Age [y:d:h:m:s]: 00:020:06:31:52 |
| Block: 3419 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5326 | RingCT/type: yes/0 |
| Extra: 01f9eeae7b290711040d5845e0c7a9918995c0604a3f9aeb034f0d14317f38a02f02090000000126697be300 | ||
1 output(s) for total of 34.955739846623 HMNY
| stealth address | amount | amount idx | tag |
| 00: 998d61759e41d6f59169547c32ff154dee57dc10ffae5892835d6294f459a435 | 34.955739846623 | 4134 of 0 | <d7> |
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": 3479,
"vin": [ {
"gen": {
"height": 3419
}
}
],
"vout": [ {
"amount": 34955739846623,
"target": {
"tagged_key": {
"key": "998d61759e41d6f59169547c32ff154dee57dc10ffae5892835d6294f459a435",
"view_tag": "d7"
}
}
}
],
"extra": [ 1, 249, 238, 174, 123, 41, 7, 17, 4, 13, 88, 69, 224, 199, 169, 145, 137, 149, 192, 96, 74, 63, 154, 235, 3, 79, 13, 20, 49, 127, 56, 160, 47, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}