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: cf8c59471f27ca9153aecbe989f11a0f57a5fcee6986b019b5c85c93691120d0
Tx prefix hash: 3e9c4774e4f96c3b143575d09d18e196a6cda2e6788fb67c4724d725ffa2cc4a
Tx public key: ec31dd96c612a936f8370a94aa81177e9955dcb9055f9065b183758bc52e0703
| Timestamp: 1779641718 | Timestamp [UTC]: 2026-05-24 16:55:18 | Age [y:d:h:m:s]: 00:015:08:40:39 |
| Block: 1356 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0820 kB |
| Tx version: 2 | No of confirmations: 6530 | RingCT/type: yes/0 |
| Extra: 01ec31dd96c612a936f8370a94aa81177e9955dcb9055f9065b183758bc52e0703 | ||
1 output(s) for total of 35.093556896165 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4bd97217962b0966c3d49ca5d70165e8581e249c23c15225fca0fe6eebe87c2b | 35.093556896165 | 1506 of 0 | <8e> |
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": 1416,
"vin": [ {
"gen": {
"height": 1356
}
}
],
"vout": [ {
"amount": 35093556896165,
"target": {
"tagged_key": {
"key": "4bd97217962b0966c3d49ca5d70165e8581e249c23c15225fca0fe6eebe87c2b",
"view_tag": "8e"
}
}
}
],
"extra": [ 1, 236, 49, 221, 150, 198, 18, 169, 54, 248, 55, 10, 148, 170, 129, 23, 126, 153, 85, 220, 185, 5, 95, 144, 101, 177, 131, 117, 139, 197, 46, 7, 3
],
"rct_signatures": {
"type": 0
}
}