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: c4afe0e6d1accbb364db509275326d8e8b81107a584bf107e96265aad9921d30
Tx prefix hash: ffdfa1402f407dc0331870ba0cc8337999a3329aaf413d3d20ae4acb5efe088e
Tx public key: be3c2f6970779c04db9f39b4febf05862a41e0c3259ebd74c960dd07350807b0
| Timestamp: 1780838700 | Timestamp [UTC]: 2026-06-07 13:25:00 | Age [y:d:h:m:s]: 00:001:09:53:53 |
| Block: 7440 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 446 | RingCT/type: yes/0 |
| Extra: 01be3c2f6970779c04db9f39b4febf05862a41e0c3259ebd74c960dd07350807b0020900000001e49593ff00 | ||
1 output(s) for total of 34.688673766971 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2012f24710357b17512b1643d1e0657a1f94f068409519e79fe15ad504ef8e32 | 34.688673766971 | 9162 of 0 | <d6> |
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": 7500,
"vin": [ {
"gen": {
"height": 7440
}
}
],
"vout": [ {
"amount": 34688673766971,
"target": {
"tagged_key": {
"key": "2012f24710357b17512b1643d1e0657a1f94f068409519e79fe15ad504ef8e32",
"view_tag": "d6"
}
}
}
],
"extra": [ 1, 190, 60, 47, 105, 112, 119, 156, 4, 219, 159, 57, 180, 254, 191, 5, 134, 42, 65, 224, 195, 37, 158, 189, 116, 201, 96, 221, 7, 53, 8, 7, 176, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}