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: 71384439f65cfd9adfc2735d9c34092382e5a024157b90b2d7089ad73cb78f86
Tx prefix hash: 595783f07fa2e34165d60138ef2bd1c2db83ea0d2849fa8808671a9676f10844
Tx public key: 5e3ae1622d71910c1e572c4ea4a341ea163303498556d00b7d7dd126c19c5241
| Timestamp: 1779660991 | Timestamp [UTC]: 2026-05-24 22:16:31 | Age [y:d:h:m:s]: 00:015:02:30:16 |
| Block: 1501 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0820 kB |
| Tx version: 2 | No of confirmations: 6385 | RingCT/type: yes/0 |
| Extra: 015e3ae1622d71910c1e572c4ea4a341ea163303498556d00b7d7dd126c19c5241 | ||
1 output(s) for total of 35.083852559988 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5275060287f9c6d602dfc18188074a6b1440a726c24c8282d0b6ffd9dc509770 | 35.083852559988 | 1657 of 0 | <c2> |
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": 1561,
"vin": [ {
"gen": {
"height": 1501
}
}
],
"vout": [ {
"amount": 35083852559988,
"target": {
"tagged_key": {
"key": "5275060287f9c6d602dfc18188074a6b1440a726c24c8282d0b6ffd9dc509770",
"view_tag": "c2"
}
}
}
],
"extra": [ 1, 94, 58, 225, 98, 45, 113, 145, 12, 30, 87, 44, 78, 164, 163, 65, 234, 22, 51, 3, 73, 133, 86, 208, 11, 125, 125, 209, 38, 193, 156, 82, 65
],
"rct_signatures": {
"type": 0
}
}