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: 18161b2f2f8fd22a8ca72395b13d1da16e115c7253b8a2847d69e17b14668881
Tx prefix hash: 60296c4d6d7610e4cecc54533f971bf9766e13e6d351e83127cf4d0a0f94e406
Tx public key: 6f9047aef7d9ea5cb8085285ec24f13025d3d039b7f64f2d86d6a3b1fea74a2c
| Timestamp: 1780125776 | Timestamp [UTC]: 2026-05-30 07:22:56 | Age [y:d:h:m:s]: 00:009:17:23:51 |
| Block: 4911 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2975 | RingCT/type: yes/0 |
| Extra: 016f9047aef7d9ea5cb8085285ec24f13025d3d039b7f64f2d86d6a3b1fea74a2c02090000000226697be300 | ||
1 output(s) for total of 34.856405368530 HMNY
| stealth address | amount | amount idx | tag |
| 00: b5f1bacb217ad54eb430eebfc97583aa180a65210ce542e73b725753e9544c9f | 34.856405368530 | 6230 of 0 | <b8> |
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": 4971,
"vin": [ {
"gen": {
"height": 4911
}
}
],
"vout": [ {
"amount": 34856405368530,
"target": {
"tagged_key": {
"key": "b5f1bacb217ad54eb430eebfc97583aa180a65210ce542e73b725753e9544c9f",
"view_tag": "b8"
}
}
}
],
"extra": [ 1, 111, 144, 71, 174, 247, 217, 234, 92, 184, 8, 82, 133, 236, 36, 241, 48, 37, 211, 208, 57, 183, 246, 79, 45, 134, 214, 163, 177, 254, 167, 74, 44, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}