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: 5c9d6f5b189e67c4b2ff74cec957ce0b8b0d088a9089e08a3f4ebdd080fb4450
Tx prefix hash: d75ab7784c03d0ce72db9c61010dc0718aff81aa8a238558c3fee01ee911101d
Tx public key: 2c406ea2afb8407b5bf78e1bc6966323d173f44dc9a701aa3c30620b0b91070d
| Timestamp: 1780043415 | Timestamp [UTC]: 2026-05-29 08:30:15 | Age [y:d:h:m:s]: 00:010:18:10:21 |
| Block: 4315 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3581 | RingCT/type: yes/0 |
| Extra: 012c406ea2afb8407b5bf78e1bc6966323d173f44dc9a701aa3c30620b0b91070d02090000000626697be300 | ||
1 output(s) for total of 34.896051993817 HMNY
| stealth address | amount | amount idx | tag |
| 00: 702cf376029511c1e12eb5a6ba7dad264959698911916b4df6ff4c8f6469a8a6 | 34.896051993817 | 5393 of 0 | <53> |
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": 4375,
"vin": [ {
"gen": {
"height": 4315
}
}
],
"vout": [ {
"amount": 34896051993817,
"target": {
"tagged_key": {
"key": "702cf376029511c1e12eb5a6ba7dad264959698911916b4df6ff4c8f6469a8a6",
"view_tag": "53"
}
}
}
],
"extra": [ 1, 44, 64, 110, 162, 175, 184, 64, 123, 91, 247, 142, 27, 198, 150, 99, 35, 209, 115, 244, 77, 201, 167, 1, 170, 60, 48, 98, 11, 11, 145, 7, 13, 2, 9, 0, 0, 0, 6, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}