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: bf21e3f8386950094c5bf82526816c8f1ae4bd9b4909fba148679aa3c30b6e38
Tx prefix hash: 64a6bf4d41c3b7a028d0011d708e69a29dcc5ab9216d9c232edde3e9e7034e6c
Tx public key: ce8933ef8eba1b6ff2f54a1d556f63df70f6763187e1f06bae8a0d0f0bc808e9
| Timestamp: 1780693013 | Timestamp [UTC]: 2026-06-05 20:56:53 | Age [y:d:h:m:s]: 00:003:03:49:54 |
| Block: 5836 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2050 | RingCT/type: yes/0 |
| Extra: 01ce8933ef8eba1b6ff2f54a1d556f63df70f6763187e1f06bae8a0d0f0bc808e9020900000001e49593ff00 | ||
1 output(s) for total of 34.794962459316 HMNY
| stealth address | amount | amount idx | tag |
| 00: 20db3b06ab66635397c73a14ec7ea9d7e6a58e03aca8c46b35210a2cb68779c9 | 34.794962459316 | 7293 of 0 | <e9> |
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": 5896,
"vin": [ {
"gen": {
"height": 5836
}
}
],
"vout": [ {
"amount": 34794962459316,
"target": {
"tagged_key": {
"key": "20db3b06ab66635397c73a14ec7ea9d7e6a58e03aca8c46b35210a2cb68779c9",
"view_tag": "e9"
}
}
}
],
"extra": [ 1, 206, 137, 51, 239, 142, 186, 27, 111, 242, 245, 74, 29, 85, 111, 99, 223, 112, 246, 118, 49, 135, 225, 240, 107, 174, 138, 13, 15, 11, 200, 8, 233, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}