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: 4be04c0f79b42c3f513a6f6f1d5ed732cf9a0e05265f63c2f52f1a3b3d765162
Tx prefix hash: 4fa025fb6f260914a253329cad85ef8a386de50108d432a40b7f3ffacfe7931b
Tx public key: cdcf7cf0253619d29d63c33340555edd0940008f35053ac18a7497e36a58a714
| Timestamp: 1780691647 | Timestamp [UTC]: 2026-06-05 20:34:07 | Age [y:d:h:m:s]: 00:003:04:12:40 |
| Block: 5743 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2143 | RingCT/type: yes/0 |
| Extra: 01cdcf7cf0253619d29d63c33340555edd0940008f35053ac18a7497e36a58a714020900000001e49593ff00 | ||
1 output(s) for total of 34.801135062184 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1c7d3bd7eb1116e8978ed61dde54365da4b8ebe00e757f16c67267431b0d7aa8 | 34.801135062184 | 7196 of 0 | <2e> |
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": 5803,
"vin": [ {
"gen": {
"height": 5743
}
}
],
"vout": [ {
"amount": 34801135062184,
"target": {
"tagged_key": {
"key": "1c7d3bd7eb1116e8978ed61dde54365da4b8ebe00e757f16c67267431b0d7aa8",
"view_tag": "2e"
}
}
}
],
"extra": [ 1, 205, 207, 124, 240, 37, 54, 25, 210, 157, 99, 195, 51, 64, 85, 94, 221, 9, 64, 0, 143, 53, 5, 58, 193, 138, 116, 151, 227, 106, 88, 167, 20, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}