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: 52afe42ca144568b6f23f17f94383c7cf83c2cdac7bb887719ea160a90205440
Tx prefix hash: a184675b782589b0cc2a53876af5cc8424d466b21e9e6d63669f24495a70dbc3
Tx public key: f4fdf261cfea9b3dfd3af68d911eb015f6b0ac56b1189f4db4dc674ef1b49474
| Timestamp: 1780799669 | Timestamp [UTC]: 2026-06-07 02:34:29 | Age [y:d:h:m:s]: 00:001:23:01:28 |
| Block: 6818 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1068 | RingCT/type: yes/0 |
| Extra: 01f4fdf261cfea9b3dfd3af68d911eb015f6b0ac56b1189f4db4dc674ef1b49474020900000003e49593ff00 | ||
1 output(s) for total of 34.729851859024 HMNY
| stealth address | amount | amount idx | tag |
| 00: bc2866a2825b9a4d1651ade307d2edc104c454b38a50fc6b1001a316e8df24ad | 34.729851859024 | 8418 of 0 | <ad> |
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": 6878,
"vin": [ {
"gen": {
"height": 6818
}
}
],
"vout": [ {
"amount": 34729851859024,
"target": {
"tagged_key": {
"key": "bc2866a2825b9a4d1651ade307d2edc104c454b38a50fc6b1001a316e8df24ad",
"view_tag": "ad"
}
}
}
],
"extra": [ 1, 244, 253, 242, 97, 207, 234, 155, 61, 253, 58, 246, 141, 145, 30, 176, 21, 246, 176, 172, 86, 177, 24, 159, 77, 180, 220, 103, 78, 241, 180, 148, 116, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}