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: bc4e9a012d5ca6504ad9cacc51c5f305bfe9101216cb5551daac47768e41c6f3
Tx prefix hash: a6faf581201c1e83a9c47a0d7e91d2b925a56b530c32cd0292fce1f4e18edb40
Tx public key: 060d693fedba96571947565fb4d4f18987e63577ecbf118841aa790f64572f77
| Timestamp: 1780690340 | Timestamp [UTC]: 2026-06-05 20:12:20 | Age [y:d:h:m:s]: 00:003:06:37:28 |
| Block: 5651 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2248 | RingCT/type: yes/0 |
| Extra: 01060d693fedba96571947565fb4d4f18987e63577ecbf118841aa790f64572f77020900000001e49593ff00 | ||
1 output(s) for total of 34.807242370395 HMNY
| stealth address | amount | amount idx | tag |
| 00: 088a57beec1d5b6e4b422e6cc61773d5736970b98e10d00fbaa93fbf7e3c35ca | 34.807242370395 | 7100 of 0 | <52> |
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": 5711,
"vin": [ {
"gen": {
"height": 5651
}
}
],
"vout": [ {
"amount": 34807242370395,
"target": {
"tagged_key": {
"key": "088a57beec1d5b6e4b422e6cc61773d5736970b98e10d00fbaa93fbf7e3c35ca",
"view_tag": "52"
}
}
}
],
"extra": [ 1, 6, 13, 105, 63, 237, 186, 150, 87, 25, 71, 86, 95, 180, 212, 241, 137, 135, 230, 53, 119, 236, 191, 17, 136, 65, 170, 121, 15, 100, 87, 47, 119, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}