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: 3c1d16810ba1b272771fe1b7aca823759604a8b9711487f09160b1747158167c
Tx prefix hash: 1fc058724b896fe8ca3a6c3e58d197acb2d1d5700ae9e69b2b5e657b32a10119
Tx public key: c35c21201a8a0edbe79064c8cd40b3969274c1936a28a758f722cf9a25542961
| Timestamp: 1780068244 | Timestamp [UTC]: 2026-05-29 15:24:04 | Age [y:d:h:m:s]: 00:010:07:54:49 |
| Block: 4613 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3273 | RingCT/type: yes/0 |
| Extra: 01c35c21201a8a0edbe79064c8cd40b3969274c1936a28a758f722cf9a2554296102090000000226697be300 | ||
1 output(s) for total of 34.876223047483 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8b9b268885de6c1a7b3717d34dcdbfbc798645f084e2298d1a7fbb2ded16f31d | 34.876223047483 | 5792 of 0 | <cd> |
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": 4673,
"vin": [ {
"gen": {
"height": 4613
}
}
],
"vout": [ {
"amount": 34876223047483,
"target": {
"tagged_key": {
"key": "8b9b268885de6c1a7b3717d34dcdbfbc798645f084e2298d1a7fbb2ded16f31d",
"view_tag": "cd"
}
}
}
],
"extra": [ 1, 195, 92, 33, 32, 26, 138, 14, 219, 231, 144, 100, 200, 205, 64, 179, 150, 146, 116, 193, 147, 106, 40, 167, 88, 247, 34, 207, 154, 37, 84, 41, 97, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}