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: 66f8f3aac0cb3d03c4ae860af0c4a62d6e7bae0bab40566d2d06ee6adc039f4f
Tx prefix hash: 9c8b2bbaa9995123c3d367be363690fc8f0199b2f83f192dcead21119e9cc912
Tx public key: 158d2a4628f192a777d2ecc412d89f9089ab64d88452383106537b05c5c33c57
| Timestamp: 1779454530 | Timestamp [UTC]: 2026-05-22 12:55:30 | Age [y:d:h:m:s]: 00:017:13:45:06 |
| Block: 368 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7529 | RingCT/type: yes/0 |
| Extra: 01158d2a4628f192a777d2ecc412d89f9089ab64d88452383106537b05c5c33c5702090000000293369e7d00 | ||
1 output(s) for total of 35.159751730471 HMNY
| stealth address | amount | amount idx | tag |
| 00: bce25e599ae7aec06a11c16f883d7b52d2acb00ddc664eb57432e58c8f118097 | 35.159751730471 | 364 of 0 | <70> |
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": 428,
"vin": [ {
"gen": {
"height": 368
}
}
],
"vout": [ {
"amount": 35159751730471,
"target": {
"tagged_key": {
"key": "bce25e599ae7aec06a11c16f883d7b52d2acb00ddc664eb57432e58c8f118097",
"view_tag": "70"
}
}
}
],
"extra": [ 1, 21, 141, 42, 70, 40, 241, 146, 167, 119, 210, 236, 196, 18, 216, 159, 144, 137, 171, 100, 216, 132, 82, 56, 49, 6, 83, 123, 5, 197, 195, 60, 87, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}