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: a9185c762e133e927981eb923a8eae91284f0869ea85262e4a8640ab69e6f82a
Tx prefix hash: bc1fe0eb46e1f4940834e90ced3bea98d2c4a2214dd16331ee7a425cf55734b0
Tx public key: d417c96c6f538c3a0b3667e741464acec4694663c95b351c48af1166601f7b72
| Timestamp: 1779643455 | Timestamp [UTC]: 2026-05-24 17:24:15 | Age [y:d:h:m:s]: 00:015:10:26:43 |
| Block: 1414 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6552 | RingCT/type: yes/0 |
| Extra: 01d417c96c6f538c3a0b3667e741464acec4694663c95b351c48af1166601f7b72020900000002ba6d17be00 | ||
1 output(s) for total of 35.089674839625 HMNY
| stealth address | amount | amount idx | tag |
| 00: 100e6f67e04bc8e485d1b8e5d4fd0b1831e9d7e5e653449446839e23aa6fc648 | 35.089674839625 | 1566 of 0 | <a3> |
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": 1474,
"vin": [ {
"gen": {
"height": 1414
}
}
],
"vout": [ {
"amount": 35089674839625,
"target": {
"tagged_key": {
"key": "100e6f67e04bc8e485d1b8e5d4fd0b1831e9d7e5e653449446839e23aa6fc648",
"view_tag": "a3"
}
}
}
],
"extra": [ 1, 212, 23, 201, 108, 111, 83, 140, 58, 11, 54, 103, 231, 65, 70, 74, 206, 196, 105, 70, 99, 201, 91, 53, 28, 72, 175, 17, 102, 96, 31, 123, 114, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}