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: 7d30a090286f9f3a29ee4ca350e8c6fc741c00e73228c0532d8171483369063f
Tx prefix hash: 860b6ca84677ab6b4d9340b9ebc59e76df6e7333e42d5fbcc733257edb0a9e56
Tx public key: 4f1726fd649c10b3d1f07f88bd156948c939ffd0e3d6132d4919cb51dd87aee8
| Timestamp: 1780825258 | Timestamp [UTC]: 2026-06-07 09:40:58 | Age [y:d:h:m:s]: 00:001:15:05:49 |
| Block: 7247 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 639 | RingCT/type: yes/0 |
| Extra: 014f1726fd649c10b3d1f07f88bd156948c939ffd0e3d6132d4919cb51dd87aee8020900000001e49593ff00 | ||
1 output(s) for total of 34.701445664927 HMNY
| stealth address | amount | amount idx | tag |
| 00: a60c682999015a9914203b8e22693b20460a4977677d3983d21e9a09abf831bf | 34.701445664927 | 8925 of 0 | <29> |
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": 7307,
"vin": [ {
"gen": {
"height": 7247
}
}
],
"vout": [ {
"amount": 34701445664927,
"target": {
"tagged_key": {
"key": "a60c682999015a9914203b8e22693b20460a4977677d3983d21e9a09abf831bf",
"view_tag": "29"
}
}
}
],
"extra": [ 1, 79, 23, 38, 253, 100, 156, 16, 179, 209, 240, 127, 136, 189, 21, 105, 72, 201, 57, 255, 208, 227, 214, 19, 45, 73, 25, 203, 81, 221, 135, 174, 232, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}