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: 58c0e3ee779f0cca878734b132ca68f325e3a20030d5319b60f088d36d43818e
Tx prefix hash: ed963eb7eadd1ce97e8ddf37e8f602f8889b490b90a3dd9476db118fdcea0d61
Tx public key: ff96f8b920fae3e9e1186e48d148422d0dea8f45a5ad5cfe9764095e1640c303
| Timestamp: 1780804628 | Timestamp [UTC]: 2026-06-07 03:57:08 | Age [y:d:h:m:s]: 00:001:23:41:42 |
| Block: 6914 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1034 | RingCT/type: yes/0 |
| Extra: 01ff96f8b920fae3e9e1186e48d148422d0dea8f45a5ad5cfe9764095e1640c303020900000001e49593ff00 | ||
1 output(s) for total of 34.723493209326 HMNY
| stealth address | amount | amount idx | tag |
| 00: ceba580f06da80340b7cfd0b5494827832751b69b405ac38c544130987dd29e8 | 34.723493209326 | 8530 of 0 | <e5> |
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": 6974,
"vin": [ {
"gen": {
"height": 6914
}
}
],
"vout": [ {
"amount": 34723493209326,
"target": {
"tagged_key": {
"key": "ceba580f06da80340b7cfd0b5494827832751b69b405ac38c544130987dd29e8",
"view_tag": "e5"
}
}
}
],
"extra": [ 1, 255, 150, 248, 185, 32, 250, 227, 233, 225, 24, 110, 72, 209, 72, 66, 45, 13, 234, 143, 69, 165, 173, 92, 254, 151, 100, 9, 94, 22, 64, 195, 3, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}