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: a564a5bf8da9d3c699e9585782def44767896cbe388565b5bde217280c12fd7e
Tx prefix hash: d221060ad8288ed5dc76d5ab3a34ece1da4ad30bbcbebcad8179a5904d64abd2
Tx public key: 63c39693c4410d38f073d5c192657822a2fa649cf1a03d341194156cbd041c77
| Timestamp: 1780752707 | Timestamp [UTC]: 2026-06-06 13:31:47 | Age [y:d:h:m:s]: 00:002:12:04:10 |
| Block: 6501 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1385 | RingCT/type: yes/0 |
| Extra: 0163c39693c4410d38f073d5c192657822a2fa649cf1a03d341194156cbd041c77020900000004e49593ff00 | ||
1 output(s) for total of 34.750856922098 HMNY
| stealth address | amount | amount idx | tag |
| 00: cc9d01c39cf7397e3295e2480c11489a1b9b52c2a1948c2a3f75ca73d28cf209 | 34.750856922098 | 7998 of 0 | <3e> |
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": 6561,
"vin": [ {
"gen": {
"height": 6501
}
}
],
"vout": [ {
"amount": 34750856922098,
"target": {
"tagged_key": {
"key": "cc9d01c39cf7397e3295e2480c11489a1b9b52c2a1948c2a3f75ca73d28cf209",
"view_tag": "3e"
}
}
}
],
"extra": [ 1, 99, 195, 150, 147, 196, 65, 13, 56, 240, 115, 213, 193, 146, 101, 120, 34, 162, 250, 100, 156, 241, 160, 61, 52, 17, 148, 21, 108, 189, 4, 28, 119, 2, 9, 0, 0, 0, 4, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}