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: eebbf745759e68fac94d29d013b6eef233571573fccbb60d727c515d968736a9
Tx prefix hash: c41cb114aa092e8c7b79520be34aa4c5896c9c2881a107f871e1e1ca02d8a59b
Tx public key: 7c97d43cbcd770db5ac1ebfae3fcaad2dc18e6b1163e5b250c05c414b0a1639a
| Timestamp: 1779952358 | Timestamp [UTC]: 2026-05-28 07:12:38 | Age [y:d:h:m:s]: 00:011:16:06:15 |
| Block: 3638 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4248 | RingCT/type: yes/0 |
| Extra: 017c97d43cbcd770db5ac1ebfae3fcaad2dc18e6b1163e5b250c05c414b0a1639a02090000000526697be300 | ||
1 output(s) for total of 34.941141542447 HMNY
| stealth address | amount | amount idx | tag |
| 00: f6f9e38f2b867636c186c1ef6d2d2a73c76c93eda61888f3407d516d62a32ccf | 34.941141542447 | 4396 of 0 | <70> |
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": 3698,
"vin": [ {
"gen": {
"height": 3638
}
}
],
"vout": [ {
"amount": 34941141542447,
"target": {
"tagged_key": {
"key": "f6f9e38f2b867636c186c1ef6d2d2a73c76c93eda61888f3407d516d62a32ccf",
"view_tag": "70"
}
}
}
],
"extra": [ 1, 124, 151, 212, 60, 188, 215, 112, 219, 90, 193, 235, 250, 227, 252, 170, 210, 220, 24, 230, 177, 22, 62, 91, 37, 12, 5, 196, 20, 176, 161, 99, 154, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}