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: ea072cb277777776606e370c9691011d51e4a776de8c1ce2adc72cd6ed78d676
Tx prefix hash: 61b4d474da4cfb4601124e6d6ec18c5a268493df9963d7fab99e9fed975cf548
Tx public key: 44312f1ea119189ae11040759ef405d12a95b882b1ddd615f463afdc48624710
| Timestamp: 1780055185 | Timestamp [UTC]: 2026-05-29 11:46:25 | Age [y:d:h:m:s]: 00:010:13:49:32 |
| Block: 4445 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3441 | RingCT/type: yes/0 |
| Extra: 0144312f1ea119189ae11040759ef405d12a95b882b1ddd615f463afdc4862471002090000000526697be300 | ||
1 output(s) for total of 34.887400396398 HMNY
| stealth address | amount | amount idx | tag |
| 00: badd2b233d6e05b93aea290a6a26fabd675f0e3f5e7e56ba9c76400eea794aa9 | 34.887400396398 | 5563 of 0 | <ca> |
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": 4505,
"vin": [ {
"gen": {
"height": 4445
}
}
],
"vout": [ {
"amount": 34887400396398,
"target": {
"tagged_key": {
"key": "badd2b233d6e05b93aea290a6a26fabd675f0e3f5e7e56ba9c76400eea794aa9",
"view_tag": "ca"
}
}
}
],
"extra": [ 1, 68, 49, 47, 30, 161, 25, 24, 154, 225, 16, 64, 117, 158, 244, 5, 209, 42, 149, 184, 130, 177, 221, 214, 21, 244, 99, 175, 220, 72, 98, 71, 16, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}