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: 681b028514e7c5114a15a0edf1ca142be6b6e142d4b30ccb1e2a6919d3bc5aae
Tx prefix hash: c783cf954695c2b71faea708ad6326a3fa1dbec5362715c72da14b097ceb41bd
Tx public key: 731256952901e5c8328edcfc957fc3ef7cecacdbe67346b0bc2482a62f33dc73
| Timestamp: 1779724810 | Timestamp [UTC]: 2026-05-25 16:00:10 | Age [y:d:h:m:s]: 00:014:09:35:47 |
| Block: 1837 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6049 | RingCT/type: yes/0 |
| Extra: 01731256952901e5c8328edcfc957fc3ef7cecacdbe67346b0bc2482a62f33dc73020900000003ba6d17be00 | ||
1 output(s) for total of 35.061375583282 HMNY
| stealth address | amount | amount idx | tag |
| 00: a041c266e308fd69ecc69c77eb1e07097d35c8df31e4965881bdd450d38de347 | 35.061375583282 | 2033 of 0 | <fd> |
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": 1897,
"vin": [ {
"gen": {
"height": 1837
}
}
],
"vout": [ {
"amount": 35061375583282,
"target": {
"tagged_key": {
"key": "a041c266e308fd69ecc69c77eb1e07097d35c8df31e4965881bdd450d38de347",
"view_tag": "fd"
}
}
}
],
"extra": [ 1, 115, 18, 86, 149, 41, 1, 229, 200, 50, 142, 220, 252, 149, 127, 195, 239, 124, 236, 172, 219, 230, 115, 70, 176, 188, 36, 130, 166, 47, 51, 220, 115, 2, 9, 0, 0, 0, 3, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}