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: e066cf81870d013e1f1af235d62e0fa32aed0a7510e35e0ed159ff07abf9cd9d
Tx prefix hash: d97336d3902e8e7eba3ec382e7e4fb1ac3676b6bb1b5266610988b6917e7952a
Tx public key: 5e14a423494ff329d52cba24bb355050959378cf2870e7b230f71e9c4ab17391
| Timestamp: 1780982391 | Timestamp [UTC]: 2026-06-09 05:19:51 | Age [y:d:h:m:s]: 00:000:08:17:45 |
| Block: 8061 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 540 | RingCT/type: yes/0 |
| Extra: 015e14a423494ff329d52cba24bb355050959378cf2870e7b230f71e9c4ab17391020900000002e49593ff00 | ||
1 output(s) for total of 34.659041783557 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6c62a674426029164d7b7c1c1ca7de8369386ad5f0f6d7cd6ace3c83eb6de9c4 | 34.659041783557 | 9989 of 0 | <bb> |
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": 8121,
"vin": [ {
"gen": {
"height": 8061
}
}
],
"vout": [ {
"amount": 34659041783557,
"target": {
"tagged_key": {
"key": "6c62a674426029164d7b7c1c1ca7de8369386ad5f0f6d7cd6ace3c83eb6de9c4",
"view_tag": "bb"
}
}
}
],
"extra": [ 1, 94, 20, 164, 35, 73, 79, 243, 41, 213, 44, 186, 36, 187, 53, 80, 80, 149, 147, 120, 207, 40, 112, 231, 178, 48, 247, 30, 156, 74, 177, 115, 145, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}