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: d2d57c4a8d6a7704d8ac13b482b53d4feb2b62ea75ff9223dedef951f80887dd
Tx prefix hash: efbe8e774cb5280425369e56a266c1fd6029a25a808da52a37cb67f18b68fb9b
Tx public key: 2cbb55e355ad458d25946402c9afec299259771c6e9c57f7e284274206776b36
| Timestamp: 1780681954 | Timestamp [UTC]: 2026-06-05 17:52:34 | Age [y:d:h:m:s]: 00:003:23:16:29 |
| Block: 5297 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3437 | RingCT/type: yes/0 |
| Extra: 012cbb55e355ad458d25946402c9afec299259771c6e9c57f7e284274206776b36020900000003e49593ff00 | ||
1 output(s) for total of 34.830752228204 HMNY
| stealth address | amount | amount idx | tag |
| 00: fe14fbd718a593fe164a287dd2469266a7f450ade2b7058e7a0216c2544d67d9 | 34.830752228204 | 6722 of 0 | <17> |
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": 5357,
"vin": [ {
"gen": {
"height": 5297
}
}
],
"vout": [ {
"amount": 34830752228204,
"target": {
"tagged_key": {
"key": "fe14fbd718a593fe164a287dd2469266a7f450ade2b7058e7a0216c2544d67d9",
"view_tag": "17"
}
}
}
],
"extra": [ 1, 44, 187, 85, 227, 85, 173, 69, 141, 37, 148, 100, 2, 201, 175, 236, 41, 146, 89, 119, 28, 110, 156, 87, 247, 226, 132, 39, 66, 6, 119, 107, 54, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}