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: dc913565cbed25fbe7ddd39fe4a47e92853e4e963f26b831c6b642753674ac76
Tx prefix hash: e9a6aeb8271167a1e434fddf5836016821316450209517ba52812272e8f6549d
Tx public key: 46f6c8804c34a8eda8e7ae62edd41775caea06e63c903538248cc04e344040d7
| Timestamp: 1780030451 | Timestamp [UTC]: 2026-05-29 04:54:11 | Age [y:d:h:m:s]: 00:010:21:46:25 |
| Block: 4195 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3702 | RingCT/type: yes/0 |
| Extra: 0146f6c8804c34a8eda8e7ae62edd41775caea06e63c903538248cc04e344040d702090000000326697be300 | ||
1 output(s) for total of 34.904039988001 HMNY
| stealth address | amount | amount idx | tag |
| 00: f3beee08c6e4be5297df4b535ee4f30bfd1fd7daf77ac10ef9cf6b124014c3ba | 34.904039988001 | 5228 of 0 | <b1> |
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": 4255,
"vin": [ {
"gen": {
"height": 4195
}
}
],
"vout": [ {
"amount": 34904039988001,
"target": {
"tagged_key": {
"key": "f3beee08c6e4be5297df4b535ee4f30bfd1fd7daf77ac10ef9cf6b124014c3ba",
"view_tag": "b1"
}
}
}
],
"extra": [ 1, 70, 246, 200, 128, 76, 52, 168, 237, 168, 231, 174, 98, 237, 212, 23, 117, 202, 234, 6, 230, 60, 144, 53, 56, 36, 140, 192, 78, 52, 64, 64, 215, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}