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: 60331e2f3592b144870d47f5c839e4cead795cd57757d6bc0e9fc8ef02b7d877
Tx prefix hash: 1342cf4dc64873464fb4e0799c40d8be749ad9882f1c4d3c7209f8f721468ecc
Tx public key: 2f1f7b7a5e93b099e3c846d664906963d9d23dc70a6bfad8760b07b784acb4c5
| Timestamp: 1779920194 | Timestamp [UTC]: 2026-05-27 22:16:34 | Age [y:d:h:m:s]: 00:020:09:48:47 |
| Block: 3349 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5396 | RingCT/type: yes/0 |
| Extra: 012f1f7b7a5e93b099e3c846d664906963d9d23dc70a6bfad8760b07b784acb4c502090000000426697be300 | ||
1 output(s) for total of 34.960407257433 HMNY
| stealth address | amount | amount idx | tag |
| 00: b445c624ccb7bbc0ee38467a7cb2477e4837aad007049d4aa12770c04a737e31 | 34.960407257433 | 4028 of 0 | <de> |
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": 3409,
"vin": [ {
"gen": {
"height": 3349
}
}
],
"vout": [ {
"amount": 34960407257433,
"target": {
"tagged_key": {
"key": "b445c624ccb7bbc0ee38467a7cb2477e4837aad007049d4aa12770c04a737e31",
"view_tag": "de"
}
}
}
],
"extra": [ 1, 47, 31, 123, 122, 94, 147, 176, 153, 227, 200, 70, 214, 100, 144, 105, 99, 217, 210, 61, 199, 10, 107, 250, 216, 118, 11, 7, 183, 132, 172, 180, 197, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}