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: fd2a70dcfd2320411bdc119339fea1e448fd50da9137d628c2f475d155964efe
Tx prefix hash: 6d9934974c5a87c64e988310b17d7c2701240df2883e2c7e5b3f76cc344c7e86
Tx public key: 1bf5969603f623d82f948225c5a180e3057ed9cdfa430d36cf05e6de7c5dc62e
| Timestamp: 1781015418 | Timestamp [UTC]: 2026-06-09 14:30:18 | Age [y:d:h:m:s]: 00:006:00:22:34 |
| Block: 8627 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 118 | RingCT/type: yes/0 |
| Extra: 011bf5969603f623d82f948225c5a180e3057ed9cdfa430d36cf05e6de7c5dc62e020900000003e49593ff00 | ||
1 output(s) for total of 34.615250979526 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4170163214f94003ad06399c3797104281e4428701821fe4e0556f44aa9e4a7b | 34.615250979526 | 10663 of 0 | <59> |
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": 8687,
"vin": [ {
"gen": {
"height": 8627
}
}
],
"vout": [ {
"amount": 34615250979526,
"target": {
"tagged_key": {
"key": "4170163214f94003ad06399c3797104281e4428701821fe4e0556f44aa9e4a7b",
"view_tag": "59"
}
}
}
],
"extra": [ 1, 27, 245, 150, 150, 3, 246, 35, 216, 47, 148, 130, 37, 197, 161, 128, 227, 5, 126, 217, 205, 250, 67, 13, 54, 207, 5, 230, 222, 124, 93, 198, 46, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}