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: dedb1ed5fd7416d8e7f1a77783af3e4de2276fd8dee267c150c430dffcfb48cb
Tx prefix hash: 1ad148f3ca3306f1b3eb8ac7f564707c8921f34cd5101cbc5d4d29a478f5f2ee
Tx public key: 59d40409c1a4ac58bb353c2346fb1e1b467c7b64d2deee5b4db2296a70f953d0
| Timestamp: 1779854110 | Timestamp [UTC]: 2026-05-27 03:55:10 | Age [y:d:h:m:s]: 00:012:21:40:47 |
| Block: 2588 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5298 | RingCT/type: yes/0 |
| Extra: 0159d40409c1a4ac58bb353c2346fb1e1b467c7b64d2deee5b4db2296a70f953d002090000000126697be300 | ||
1 output(s) for total of 35.011188913812 HMNY
| stealth address | amount | amount idx | tag |
| 00: dd66b4d6c95cdb103ec3db8e18007817274a512d7815140aea6586f77b57ed70 | 35.011188913812 | 3046 of 0 | <87> |
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": 2648,
"vin": [ {
"gen": {
"height": 2588
}
}
],
"vout": [ {
"amount": 35011188913812,
"target": {
"tagged_key": {
"key": "dd66b4d6c95cdb103ec3db8e18007817274a512d7815140aea6586f77b57ed70",
"view_tag": "87"
}
}
}
],
"extra": [ 1, 89, 212, 4, 9, 193, 164, 172, 88, 187, 53, 60, 35, 70, 251, 30, 27, 70, 124, 123, 100, 210, 222, 238, 91, 77, 178, 41, 106, 112, 249, 83, 208, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}