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: cfe537827ac1e5c08d82aea926cadbe861d56c0a4b2bd7fa1f70c18ed63a0371
Tx prefix hash: c41ad90662b415895c0ace8e0c1ef547fce7100aa269d8dbc7d287c60b7a9556
Tx public key: a6732a211ddb862c597c79f5a058a979d493c3e796d98fa33db505329429dfaf
| Timestamp: 1780687760 | Timestamp [UTC]: 2026-06-05 19:29:20 | Age [y:d:h:m:s]: 00:003:03:49:33 |
| Block: 5497 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2389 | RingCT/type: yes/0 |
| Extra: 01a6732a211ddb862c597c79f5a058a979d493c3e796d98fa33db505329429dfaf020900000001e49593ff00 | ||
1 output(s) for total of 34.817467871957 HMNY
| stealth address | amount | amount idx | tag |
| 00: b7214d22bfa2b8c1f7038cd60100891b1db21d6e05fbd8d3df79861652e3dd4f | 34.817467871957 | 6936 of 0 | <47> |
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": 5557,
"vin": [ {
"gen": {
"height": 5497
}
}
],
"vout": [ {
"amount": 34817467871957,
"target": {
"tagged_key": {
"key": "b7214d22bfa2b8c1f7038cd60100891b1db21d6e05fbd8d3df79861652e3dd4f",
"view_tag": "47"
}
}
}
],
"extra": [ 1, 166, 115, 42, 33, 29, 219, 134, 44, 89, 124, 121, 245, 160, 88, 169, 121, 212, 147, 195, 231, 150, 217, 143, 163, 61, 181, 5, 50, 148, 41, 223, 175, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}