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: d2c3b472a2275ed82278cacbfb8c1e9e211cbee8ed448facef07f4e383966830
Tx prefix hash: 5a0056ca58841f5ad4934f6cfc2f1637286b14ae04d84832f5af54ce62d0c92d
Tx public key: dfa70f3a82a33855ac7d64f3d47feac43971deacc195bbccc9f62407a71445d5
| Timestamp: 1779802656 | Timestamp [UTC]: 2026-05-26 13:37:36 | Age [y:d:h:m:s]: 00:013:13:12:12 |
| Block: 2316 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5604 | RingCT/type: yes/0 |
| Extra: 01dfa70f3a82a33855ac7d64f3d47feac43971deacc195bbccc9f62407a71445d502090000000126697be300 | ||
1 output(s) for total of 35.029357407408 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2c91a5541346961672db7e0f718656f0d919bcaa9268720a3f2ab00357180d4f | 35.029357407408 | 2706 of 0 | <bf> |
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": 2376,
"vin": [ {
"gen": {
"height": 2316
}
}
],
"vout": [ {
"amount": 35029357407408,
"target": {
"tagged_key": {
"key": "2c91a5541346961672db7e0f718656f0d919bcaa9268720a3f2ab00357180d4f",
"view_tag": "bf"
}
}
}
],
"extra": [ 1, 223, 167, 15, 58, 130, 163, 56, 85, 172, 125, 100, 243, 212, 127, 234, 196, 57, 113, 222, 172, 193, 149, 187, 204, 201, 246, 36, 7, 167, 20, 69, 213, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}